Assigning String Variables and Global Variables to the Same Pipeline Variable
You can use global variable substitution and pipeline variable substitution for the same pipeline variable. That is, you can assign a pipeline variable of type String and a global variable to the same pipeline variable of type String, String List, or String Table. For example, you might assign a pipeline variable the following value: %myGlobalVariable% %myString% where myGlobalVariable is a global variable defined on Integration Server and myString is a variable that exists in the pipeline.
Keep the following information in mind when performing global variable substitution and pipeline variable substitution for the same variable.
To instruct
Integration Server to perform global variable substitution and pipeline variable substitution, you must select the
Perform global variable substitution check box
and the
Perform pipeline variable substitution check box.
If the specified global variable has the same name as a pipeline variable name and you select the
Perform global variable substitution check box
and the
Perform pipeline variable substitution check box,
Integration Server uses the value of the pipeline variable at run time.
If the pipeline variable that you specified does not exist in the pipeline at run time,
Integration Server looks for a global variable with that name. If a global variable with that name is not defined in
Integration Server, at run time
Integration Server throws an exception and service execution fails
For example, suppose that you specify %myGlobalVariable% %myString% where myGlobalVariable is a global variable defined on Integration Server and myString is a variable that exists in the pipeline. You also select the Perform global variable substitution check box and the Perform pipeline variable substitution check box. At run time, if Integration Server cannot find a String pipeline variable named myString, Integration Server looks for a global variable named myString. If a global variable named myString does not exist on that Integration Server then Integration Server throws an exception and service execution fails.
If you anticipate that the pipeline variable that you want to use as the value pf another pipeline variable might not exist in the pipeline at run time, do not perform pipeline variable substitution an global variable substitution for that variable in the same flow step.