When you map fields in a mapping, mapplet, or task, the Field Mapping Type menu is incorrectly labeled. The menu should be labeled “Options”. To configure how fields display and which fields to display, click

Field Mapping Type

.

On the

Input Parameters

page in a mapping task, expressions that include a field name with a special character cause an “invalid token” validation error.

In a

data filter rule

, if a data element classification is mapped to more than one data element, an error occurs when you try to run a mapping in

Data Integration

with an Access Policy transformation. The

data filter rule

is unable to determine which column to filter on.

When running a mapping that includes an Access Policy transformation in

Data Integration

, an error occurs if the name of a column in the source has special characters.

When creating a mapping that includes an Access Policy transformation in

Data Integration

, a nondescript error appears if you do not have the

Data Marketplace

Role and you attempt to select user type.

Precision and scale settings made in SQL transformations during the May 2025 release are ignored.

Users who don't have access to a dynamic mapping task or a data transfer task are able to add the task to the Data Task step in a taskflow and run the taskflow successfully.

A mapping that contains a Machine Learning transformation fails if it runs during an upgrade window. After the Secure Agent services are upgraded to the latest version, the mapping runs successfully again.

To delete a mapping, a user’s role incorrectly requires Read, Update, and Delete privileges on mappings instead of only Read and Delete privileges.

The Client ID and Client Secret fields are available when you create the SQL server connection from the data catalog. They're unvailable when you create the SQL server connection from the Connection page using SQL Server Authentication mode in Administrator. These fields should only be available in Service Principal Authentication mode.