Mappings

Back Next

Parameter scope

When you define values for the same parameter in multiple sections in a parameter file, the parameter with the smallest scope takes precedence over parameters with larger scope.

In this case,

Data Integration

gives precedence to parameter values in the following order:

Values defined in a task section.

Values defined in a taskflow

or linear taskflow

section.

Values defined in the #USE_SECTIONS section.

Values defined in a global section.

For example, a parameter file contains the following parameter values:

[GLOBAL]
$$connection=ff5
[Project1].[Folder1].[monthly_sales]
$$connection=ff_jd

For the task "monthly_sales" in Folder1 inside Project1, the value for parameter $$connection is "ff_jd." In all other tasks, the value for $$connection is "ff5."

If you define a parameter in a task section and in a taskflow

or linear taskflow

section and the taskflow uses the task,

Data Integration

uses the parameter value defined in the task section.

For example, you define the following parameter values in a parameter file:

#USE_SECTIONS
$$source=customer_table
[GLOBAL]
$$location=USA
$$sourceConnection=Oracle
[Default].[Sales].[Task1]
$$source=Leads_table
[Default].[Sales].[Taskflow2]
$$source=Revenue
$$sourceconnection=ODBC_1
[Default].[Taskflow3]
$$source=Revenue
$$sourceconnection=Oracle_DB

Task1 contains the $$location, $$source, and $$sourceconnection parameters. Taskflow2 and Taskflow3 contain Task1.

When you run Taskflow2,

Data Integration

uses the following parameter values: