You can parameterize the connection, objects, and the advanced runtime properties in mappings.
Consider the following rules and guidelines when you use parameterization:
General guidelines
- When you create a mapping with a parameterized target that you want to create at runtime, set the target field mapping to automatic.
- You cannot parameterize the field mapping.
Mappings
When you use input parameters, specify the parameter name in the following format:
- When you use input parameters, specify the parameter name in the following format:
▪ Format in a mapping task: $name$
▪ Format in a parameter file: $name
- When you use in-out parameters, specify the parameter name in the following format in a mapping task or a parameter file: $$name.
Mappings in advanced mode
- When you use input parameters, specify the parameter name in the following format in a mapping task: $name$.
- When you create a target at runtime, you cannot parameterize the target object.
- You cannot use input parameters in a parameter file to parameterize the source filter, custom query, multiple objects, and advanced properties at runtime.
- Ensure that you create the parameter before you override it using a parameter file.
- You cannot parameterize only the connection. You can either parameterize both the connection and the object or only the object.
- When you parameterize the object, ensure that the metadata of the imported object matches the metadata fetched in the override.
- When you use the parameter file to parameterize the source or target objects, you must specify the absolute path of the objects.
For example, $$SrcObj=<table name>;
- When you parameterize the connection or object, ensure that the connection or object that you want to override exists in Microsoft Azure Synapse SQL.