Microsoft Fabric Data Warehouse Connector > Migrating a mapping > Migrate a mapping to a different path
  

Migrate a mapping to a different path

You can use a different object path to run the mapping from the new environment.
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. 1Runtime advanced attributes. The advanced properties such as schema and table in the Source or Target transformation in a mapping.
  2. 2Connection attributes. Attributes such as database and schema set in the connection properties.
  3. 3Object metadata. The object selected in the Source or Target transformation in a mapping.

Migration options

When you migrate to a different path, 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 from, for example, Org 1, into a new organization, for example, Org 2, you can change the existing connection in the Review Connections section to map to the connection that has access to the specified 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 in the new organization 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. When you use a parameter file, you can save the parameter file on a local machine or in a cloud-hosted directory. 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
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
When you parameterize both the advanced properties and the object, 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.

Migration restrictions

Consider some rules for some of the configurations before you migrate assets: