Data Integration Release Notes > Fixed issues
  

Fixed issues

The tables in this section describe recent fixed issues for Data Integration. Note that some releases might not include fixes.

February 2025 fixed issues

Issue
Description
CDAM-2753
When running a mapping that includes an Access Policy transformation in Data Integration, the following error appears when you click Validation in the Mapping window:
Failed to create the following transformation:
AccessPolicy (AccessPolicy) - An error occurred processing the asset referenced by AccessPolicy (401 - 401 Unauthorized:
"{"statusCode":401,"code":"UNAUTHORIZED","message":"Authentication token not provided.","serviceVersion":"1.0.0.9"}")
Despite the error, the mapping executes correctly. You can ignore the error.

November 2024 fixed issues

Issue
Description
CDAM-2915
When you try to select a consumer while creating a mapping that includes an Access Policy transformation in Data Integration, and you don’t have any Administrator role, you receive an undefined error. You can still create and run the mapping, but the consumer’s name will not appear in the Consumer field. An ID appears instead.

October 2024 fixed issues

Issue
Description
CDAM-2629
When running a mapping that includes an Access Policy transformation in Data Integration, an error occurs if the transformation includes a data filter policy that uses any of the following operators on a date data type:
  • - is any of
  • - is greater than
  • - is greater than or equal to
  • - is less than
  • - is less than or equal to
  • - is none of
No error occurs if the data filter policy uses any of the following operators on a date data type:
  • - is null
  • - is not null
CDAM-2560
After you create a mapping that includes an Access Policy transformation in Data Integration, if you add parameters in the source, this change is not reflected in the output.
CDAM-1224
When you run a mapping in Data Integration that includes any binary or varbinary data type, the mapping fails with an error.
ISD-5516
When you parse a PDF document that contains tables created in Microsoft Excel, Intelligent Structure Discovery doesn't detect the data correctly.
ISD-5498
When you use an intelligent structure model in a Structure Parser transformation to read a PDF document, even though the mapping correctly writes to the target, the session log displays the following error:
[ERROR] May 02, 2024 4:10:01 PM org.apache.fontbox.ttf.gsub.GlyphSubstitutionDataExtractor putNewSubstitutionEntry