Mapping mode provides an overview of a transformation mapping and the basic tools to perform the mapping. Also see Common Mode Elements for elements of the user interface that are shared by multiple display modes.
Mapping mode is the default display mode when opening a transformation for configuration.
In mapping mode, the left side contains the source structure and variables available to be used within the mapping of the target structure on the right side:
To return to mapping mode while in script mode, click the arrow on the left side of the screen:
In mapping mode, the left side of the transformation displays the source schema, while the right side displays the target schema. These schemas can be defined either within an activity that is located adjacent to the transformation, or directly within a transformation. If a schema has not yet been defined, you will be presented with the options below for the source or target side, respectively.
|NOTE: A target schema must be specified prior to being able to configure a transformation mapping.|
It is not required to specify a source schema (see When to Use a Schema). If you don't want a source schema to be used, you don't need to do anything with the source side of the transformation.
If you have not specified a source schema and want to specify one, you can return to the workflow to provide a schema within an activity located adjacent to the transformation, or select one of these options:
A target schema must be specified prior to being able to configure a transformation mapping (see When to Use a Schema).
A defined target schema is made up of nodes that can contain fields, as well as other, child nodes that can contain fields. Source data cannot be mapped to the target nodes themselves, but can be mapped only to the fields they contain. Once you have defined a target schema, to access options available on each node, hover over the target node, then click the actions menu icon to show the actions menu. Each action is described below.
Duplicate mapping node: Available only on nodes whose cardinality indicates they can occur more than once (with the exception of the root node), this will duplicate the node and its fields, as well as any child nodes and their fields. This option is typically used for the purposes of creating additional nodes to map a denormalized source to a hierarchical target.
For a transformation mapping to result in output data from the transformation, you must map to at least one field in the target schema. Once you have defined a target schema, you can map to the target fields in any of the ways covered below, including by mapping source objects, variables, scripts, or custom values to the target fields or adding other script logic:
$) preceding the variable name.