After you add a mapping to a workflow, you can bind mapping outputs to workflow variables. You can pass the values to other tasks in the workflow.
For example, you might want the Data Integration Service to evaluate the mapping output value and then determine which object to run next. Or, you might want the Data Integration Service to use the mapping output value in a field in the next task.
To use the mapping output in another task, bind the mapping output to a workflow variable in the Mapping task
Output
view.
If you assign a mapping output to a workflow variable and the mapping processes no rows, the output is NULL. The mapping task does not change the value of the workflow variable. The variable retains the same value as it was before the Mapping task ran.
The following image shows the Mapping task
Output
view.
The
Output
column contains the following types of mapping outputs:
System-Defined Mapping Outputs
Built-in mapping outputs that the transformations return to the mapping. The system-defined mapping outputs contain the number of source rows, the number of target rows, and the number of error rows the mapping processed.
User-Defined Mapping Outputs
You can bind persisted mapping output values and current mapping output values to workflow variables.
Persisted Values
The user-defined mapping output values from the previous workflow run. The persisted value is a value that is in the repository from the last time the Mapping task ran. The persisted value is not the value that the current mapping aggregates.
Current Values
The user-defined mapping output values from the current Mapping task.
For more information about workflow variables, see the