Mappings

Back Next

Rules and guidelines for parameter files

Data Integration

uses the following rules to process parameter files:

If a parameter isn't defined in the parameter file,

Data Integration

uses the value defined in the task.

If a mapping uses a source or target object parameter that can be overridden at runtime and an existing object is selected in the task, the parameter value in the parameter file can't be null. If the value is null, the task fails.

In advanced mode, you can't set input parameter values in a parameter file. If you override an in-out parameter in a parameter file that relies on an input parameter value, make sure the in-out parameter value is valid based on the input parameter values that you configure in the

mapping

task. Otherwise, the mapping might fail.

For example, if the source connection is an input parameter and the source table is an in-out parameter, the table name that you configure in the parameter file must exist in the source connection that you set in the

mapping

task.

In advanced mode, make sure that default parameter values are valid for schema and table names. If you use a parameter file to update the parameter value for a schema name or table name override and the default parameter value is invalid, the mapping fails.

Data Integration

processes the file top-down.

If a parameter value is defined more than once in the same section,

Data Integration

uses the first value. For example, a parameter file contains the following task section:

[MyProject].[Folder1].[mapping_task1]
$$sourceconn=Oracle
$$filtervariable=ID
$$sourceObject=customer_table
$$targetconn=salesforce
$$sourceconn=ff_2

When mapping_task1 runs, the value of the sourceconn parameter is Oracle.

If a parameter value is another parameter defined in the file, precede the parameter name with one dollar sign ($).

Data Integration

uses the first value of the variable in the most specific scope. For example, a parameter file contains the following parameter values:

[GLOBAL]
$$ffconnection=my_ff_conn
$$var2=California
$var5=North
[Default].[folder5].[sales_accounts]
$$var2=$var5
$var5=south

In the task "sales_accounts," the value of "var5" is "south." Since var2 is defined as var5, var2 is also "south."

In advanced mode, precede the parameter name with two dollar signs ($$):

[GLOBAL]
$$ffconnection=my_ff_conn
$$var2=California
$$var5=North
[Default].[folder5].[sales_accounts]
$$var2=$$var5
$$var5=south

If a task is defined more than once,

Data Integration

combines the sections.

If a parameter is defined in multiple sections for the same task,

Data Integration

uses the first value. For example, a parameter file contains the following task sections:

[Default].[Folder1].[MapTask2]
$$sourceparam=Oracle_Cust
 
[Default].[Folder1].[MapTask2]
$$sourceparam=Cust_table
$$targetparam=Sales

When you run MapTask2,

Data Integration

uses the following parameter values:

$$sourceparam=Oracle_Cust

$$targetparam=Sales

The value of a parameter is global unless it is present in a section.

Data Integration

ignores sections with syntax errors.

The default date/time format for a mapping in advanced mode is MM/DD/YYYY HH24:MI:SS. To use a different date/time format, configure the advanced session property

DateTime Format String

in the

mapping

task.

Parameter files

Download Guide

Watch

Comments

Cloud Data Integration Homepage

Free Trial

Communities

Knowledge Base