Microsoft Azure Synapse SQL Connector > Migrating a mapping > Use a different object path for the migrated mapping
  

Use a different object path for the migrated mapping

After you migrate the mapping, you can use a different object path to run the mapping from the new environment. In this scenario, before you migrate the mapping, you can change the object metadata, runtime attributes, or the connection attributes to reflect the object path in the migrated environment. You do not have to edit or update the mapping in the new environment.
As a rule, when you specify the schema or table in the advanced properties, connection, or object properties, Data Integration honors the attributes in the following order of precedence:
  1. 1. Runtime advanced attributes. The advanced properties such as schema and table in the Source, Target, or Lookup transformation in a mapping.
  2. 2. Connection attributes. Attributes such as database and schema set in the connection properties.
  3. 3. Object metadata. The object selected in the Source, Target, or Lookup transformation in a mapping.
When you migrate a mapping, ensure that the metadata of the imported object matches the metadata fetched in an override.

Migration options

When you migrate, you can choose from one of the following options to update the object path:

Option 1. Update the connection properties to reference the new object

When you import the mapping into Org 2, in the Review Connections section, you can change the existing connection to map to the connection that has access to the schema and table in Org 2.

Option 2. Override the properties from the advanced properties

Before the migration, specify the required schema and table name for the object from Org 2 in the advanced properties of the Org 1 mapping.
After the migration, when you run the mapping, the Secure Agent uses the configured advanced parameters to override the object specified in the mapping imported from Org 1.

Option 3. Parameterize the properties in the mapping

You can choose to parameterize the advanced attributes, such as the schema and table name before the migration. You can configure input parameters, in-out parameters, and parameter files in the mapping. After you migrate the mapping, do not edit or update the mapping. If you have used in-out parameters for the advanced attributes such as for the schema and table name, you can update these from the parameter file.
Parameterizing only the advanced properties, but not the object or connection in the mapping
You can choose to parameterize only the advanced properties before the migration, and use them at runtime. After the migration, when you run the mapping, the Secure Agent uses the value of the parameters specified in the advanced properties.
Parameterizing both the advanced properties and the object or connection
When you parameterize both the advanced properties and the object or connection, you can choose to select or deselect the Allow parameter to be overridden at runtime option.
Allow parameter to be overridden at runtime option is selected
When you parameterize both the advanced properties and the object or connection and select the Allow parameter to be overridden at runtime option before the migration, you must select a placeholder object in the object properties in the mapping and then specify an override to this placeholder object from the advanced properties. Ensure that the placeholder object contains the same metadata as the corresponding table that you specify as an override. When you run the mapping, the value specified in the advanced property overrides the placeholder object.
Allow parameter to be overridden at runtime option is not selected
When you parameterize both the advanced properties and the object or connection and do not select the Allow parameter to be overridden at runtime option before the migration, you do not need a placeholder object and the values specified in the advanced properties take precedence.

Parameterization rules

Consider the following rules to parameterize the object and advanced properties:

General rules and guidelines

Applicable object types, transformations, and fields
The following table lists the transformation, object type, and the fields in the advanced properties of a mapping that you can retain when you migrate to the new environment:
Transformations
Object type
Source
Single object, multiple objects
Lookup
Single object
Applicable for unconnected, and connected cached and uncached.
Target
Single object
Note: Advanced fields such as the schema and table name are supported for the Source, Lookup, and Target transformations.
Multiple sources
Consider the following guidelines:
Advanced filter and table name override combination
If the mapping contains an advanced filter for the object, for example, <Table2>, in the query options section and an override to the table name in the advanced properties, consider the following rules to override the table:
In mappings, consider one of the following options:
In elastic mappings, use the table name specified as an override in the advanced properties directly in the advanced filter condition. For example, <Table2>.id >= 1
SQL override
In the mapping, do not specify an SQL override when the object type is a custom query. A mapping with this combination fails.
Schema change handling
You cannot dynamically refresh the data object schema at runtime. You must maintain the same metadata for the table selected in the source, target, or lookup transformations and the corresponding advanced field overrides, as schema change handling is not applicable.