Data Integration Release Notes > Known issues
  

Known issues

The tables in this section describe known issues for Data Integration. Not all monthly releases include known issues.

October 2025 known issues

Issue
Description
CLDDI-46863
A mapping fails to run when all of the following conditions are true:
  • - The mapping is configured to preserve special characters in native field names.
  • - A Target transformation uses manual field mapping to write to an existing Oracle target.
  • - A field name in the Target transformation contains an at sign (@).
Workaround: Use an Expression transformation before the Target transformation to rename the field that has the at sign.
CLDDI-46768
A mapping fails to run when all of the following conditions are true:
  • - The mapping is configured to preserve special characters in native field names.
  • - A Target transformation uses manual field mapping to write to an existing Oracle target.
  • - A field name in the Target transformation contains a right parenthesis character ( ')' ).
CLDDI-46433
When you view a mapping task and you don't have Read privileges for the mapping that the task is based on, the mapping image doesn't appear.
CLDDI-46080
When you configure a mapping with a Union transformation to preserve special characters in native field names, the following issues occur:
  • - In the mapping task, the Input Parameters page isn’t available when the Union transformation uses parameterized field mappings.
  • - The mapping fails if you manually map the fields in the Union transformation.
    • Workaround: Add an Expression transformation to the end of each incoming source pipeline before the Union transformation. In the Expression transformations, configure the fields that you want to map to use the same names in each transformation.
CLDDI-45988
If your organization uses the JWT authentication type, when you start the mapping creation process in Business 360 Console, Data Integration doesn't automatically map the fields between the source and target transformations.
CLDDI-45986
If your organization uses the JWT authentication type and you use a catalog source in a mapping or task, you can’t update the catalog source in Metadata Command Center.
CLDDI-45485
When you create expression fields in a mapping task, you can’t include special characters in the field name.
Workaround: Create expression fields with special characters in the field name in the mapping.

July 2025 known issues

Issue
Description
CDGC-82861
Data de-identification policies automatically inherit stakeholders from the associated precedence tiers. Although the user interface does not display these stakeholders, you can still initiate a workflow.

May 2025 known issues

Issue
Description
INTAI-134
When you import or export a mapping that contains a Vector Embedding transformation with a Large Language Model connection, the connection doesn’t appear in the asset list and isn’t imported or exported, respectively.
Workaround: After you import the mapping, recreate or reconfigure the Large Language Model connection in the Vector Embedding transformation.

February 2025 known issues

Issue
Description
CLDDI-40046
When a task uses a connection with an SSL-enabled endpoint and the task runs in a serverless runtime environment, an "Error loading the keystore" error occurs.
POP-65000
If you log in using OAuth and you include a commit tag when you check in an object to an Azure DevOps repository, the check-in action fails.
Workaround: Log in using a personal access token that permits use of commit tags.