With this release, you can now specify which type of IDs of d.velop documents should be used for mapping. As of version Annual 2025, d.velop documents (on-premises) returns two types of IDs simultaneously when retrieving data. With a new parameter you can filter the IDs.
New functions and enhancements
ID 18892: Control the filtering of the d.velop IDs with parameter in the connection string
You can now specify in edoc content services in the module d.velop documents, d.velop cloud (REST-API) with the parameter idmapping in the connection string which type of d.velop IDs is used: UUIDs or legacy IDs. Use the parameter to filter the data records according to an ID format.
The following options are available:
-
idmapping=legacy: Returns the IDs in the ID structure specified by your system.
-
idmapping=uuid: Returns the IDs in UUID format.
-
idmapping=null or not specified: With this option, nothing is filtered. The returned data can contain both the legacy IDs and UUIDs. The mixed d.velop IDs correspond to the d.velop standard behavior.
Bug fixes and improvements
No bugs were fixed in this release.