You are here:

Target Variables

Target variables enable you to reference data from a record field or from within a formula that was set or retrieved in a previous step.

A Target variable is associated with a specific target field and is populated in one of two ways:

Links — A Target variable can be populated with the result of a link or formula on a link from a target field.
Target Data Retrieval — A variable can retrieve data directly from the target using a SEEK step, which returns all target fields and any of those field values can be written to a Target variable. Some adapters retrieve certain target data after any type of step. For example, the Adapter for Dynamics CRM returns the ID that is generated when most records are created or updated. With these adapters, you can populate a Target variable with the ID retrieved from the target during Insert and Update steps.

Note:

To use a connection in a variable, that connection must be used in some role in the current DTS. Usage codes in the Connection Manager indicate the roles connections have in the current DTS, such as source, target, or rejected row.

If you want to use a connection in a variable but that connection does not have a role in the current DTS, add the connection to the DTS as a target in the Configure Steps window. You do not need to define any steps for this connection.

Executed steps may retrieve and return values from the target database if the procedure or method permits. If the method returns data, the Insight adapter being used determines if that data can populate a Target variable.

A Target variable is associated with a particular target field on an entity. If you have multiple steps against the same entity, you can either configure a particular step to populate a Target variable, populate the Target variable in the last successful step, or allow the Insight processing logic to populate the variable.

Target variables can be useful for:

Setting a lookup link value to a primary key generated by a previous step. For example, if you import company and contact data together with two separate steps and want to search for contact matches within the same company.
Assigning foreign keys to a value from a previous step when the value is not automatically assigned. For example, importing company to company relationships.
Setting a foreign key for an update step.
Reading a target value to concatenate additional data onto the end of a field.

Note:

Using Target variables increases processing time. However, in most cases, this is preferable to running two jobs to accomplish the same result.
Target Variables do not support binary data. The maximum supported length is 16K characters.
This feature requires special handling when working with bulk operations. See Using Bulk Operations for more information.