Changed behavior

When you convert a PowerCenter mapping with a non-parameterized flat file target set to create the file at runtime, the converted mapping now uses the native field-ordering target property of Cloud Data Integration to match the original PowerCenter column order.

Previously, the converter inserted an extra Expression transformation before the target to reorder the fields.

For more information, see PowerCenter Modernization.

In Oracle, Microsoft SQL Server, and ODBC connections, when a source or target has the schema name or table name overridden at the session level, the converter now retains the overridden schema name and table name into the mapping task instead of parameterizing the source or target. This behavior applies when you set OverrideOwnerNameSessionAttribute=false and OverrideTableNameSessionAttribute=false. After conversion, the retained schema name and table name appear under Advanced Properties of the mapping task.

Previously, when you used these flags, the converter created non-parameterized objects but ignored the schema name and table name from the session.

For more information, see PowerCenter Modernization.

The default value of the HandleLKPOutputPortDefaultValue conversion property is now set to true since the property applies only to cloud data warehouse lookups.

Previously, the default value was false and the migration team had to set the property manually for cloud data warehouse repointing tasks.

For more information, see PowerCenter Modernization.

When you convert mappings that contain a flat file target configured as Create New at Runtime, the converter now enables the Skip Rounding for decimal and double datatypes property on the target by default.

Previously, the converter did not set this property automatically.

For more information, see PowerCenter Modernization.

When you convert a PowerCenter mapping with a connected lookup transformation on a Snowflake or Google BigQuery connection that has a default value on the return field, the converted mapping now sets the default value directly in the lookup return field metadata and enables the Use Lookup Field Default Value property.

Previously, the converter added an extra expression transformation after the lookup transformation to substitute the default value when the lookup returned null.

For more information, see PowerCenter Modernization.