OData Integration Update: Translation Corrections (May 26, 2025)
Update your queries to prepare for upcoming changes to translations affecting the OData integration.
Background
On March 24, 2025, we rolled out translation corrections to all workspaces related to the capitalization of letters for several default fields in the meta model (for example, “End of Life” replaced “End of life”). However, for the OData integration, we continued exporting the former values to ensure continued support with the BookmarkService.svc endpoint.
Upcoming Changes
On May 26, 2025, we will switch to new translation values for the OData integration. Affected fields are listed below. These fields will be exported with their new default spelling unless otherwise customized.
Additionally, with the same release, we will start supporting singular placeholders. Currently, when using singular naming convention placeholders (for example, {{targetFactSheet}}) in the name of a relation, the placeholder is exported as-is in OData. Starting May 26, 2025, 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. If you have questions or need help, please contact support.
Recommendation
We recommend using the BookmarkService.svc OData endpoint. It exports key values instead of translations, ensuring keys stay static even if translation corrections occur. To learn more about supported endpoints, see OData Endpoints.
Affected Fields
All Fact Sheet Types
| Key | Old Value | New Value |
|---|---|---|
relToParent | Parents | Parent |
lifecycle:phaseIn | Phase in | Phase In |
lifecycle:phaseOut | Phase out | Phase Out |
lifecycle:endOfLife | End of life | End of Life |
Application Fact Sheet
| Key | Old Value | New Value |
|---|---|---|
lxStatusSSO | Single Sign On - Availability | Single Sign-On - Availability |
lxSsoProvider | Single Sign On - Available Providers | Single Sign-On - Available Providers |
Business Context Fact Sheet
| Key | Old Value | New Value |
|---|---|---|
category | Warning type | Warning Type |
warningSubType | Warning subtype | Warning Subtype |
warningCriticality | Warning criticality | Warning Criticality |
Interface Fact Sheet
| Key | Old Value | New Value |
|---|---|---|
dataFlowDirection | Data flow direction | Data Flow Direction |
Transformation Fact Sheet (Legacy)
| Key | Old Value | New Value |
|---|---|---|
yearlyTailCost | Annual follow-up cost | Annual Follow-Up Cost |
relativeStartDate | Relative start date | Relative Start Date |
budgetAfterPlanning | Budget after Planning | Budget After Planning |
Relations
| Relation | Key | Old Value | New Value |
|---|---|---|---|
| Business Capability / Transformation (legacy) | relBusinessCapabilityToTransformation | Improved by | Improved By |
| Business Capability / Objective | relBusinessCapabilityToObjective | Improved by | Improved By |
| IT Component / Tech Category | itComponentTechnologyStackRelation:supportType | Support type | Support Type |
| Business Capability / Objective | relBusinessCapabilityToObjective:supportType | Support type | Support Type |
| Transformation Requires (legacy) | requiresTransformationRelation:supportType | Support type | Support Type |
| IT Component / User Group | itComponentUserGroupRelation:numberOfUsers | Number of users | Number of Users |
| IT Component / Organization | itComponentOrganizationRelation:numberOfUsers | Number of users | Number of Users |
| IT Component / User Group | itComponentUserGroupRelation:usageType | Usage type | Usage Type |
| IT Component / Organization | itComponentOrganizationRelation:usageType | Usage type | Usage Type |
Updated 1 day ago