Switch to corrected field translations for the OData integration on May 26

On March 24, we rolled out translation corrections to all workspaces related to the capitalization of characters for several default fields in the meta model  (e.g., 'End of Life' replaced 'End of life'). However, for our OData integration, we continued to export the former values to ensure continued support with the BookmarkService.svc endpoint. On May 26, we will switch to the new values for the OData integration. The 17 fields listed in our user documentation are affected and will be exported with their new default spelling unless otherwise customized.

We recommend using our other OData endpoint, BookmarkDataService.svc. It exports the key values instead of translations, and keys will remain static regardless of translation corrections. For more information and use cases, please visit our updated documentation on the OData integration.

Furthermore, with the same release, we will start supporting the use of singular placeholders. Currently, when using singular naming convention placeholders (e.g., {{targetFactSheet}}) in the name of a relation, the placeholder is exported as-is in OData. Starting May 26, these placeholders will be resolved to the corresponding fact sheet type.

Please assess and adapt your business Intelligence queries and adjust the data references to the new values as needed to ensure your integration flows are not interrupted.