Skip to end of metadata
Go to start of metadata

Introduction

Source fields can be manually mapped to a target field in either mapping mode or script mode. When you map a source field, the reference path of the source object is inserted into a script on the target field. Automatic mapping of a source object to a target field is covered in Automapping.

Mapping to a Target Field

To manually map a source field in mapping mode, within the Source tab on the left, drag a source object on the left to an appropriate target field on the right:

To manually map a source object in script mode, within the Source Objects tab on the right, drag a source object on the right to an appropriate target field on the left:

In both modes, the mapped source object is visually displayed within the target field, with a script icon  added in the top right to indicate the field has a mapping:

To view or edit the mapping as a script, click the script icon  to open the editable script area for the target field in script mode:

An alternative to drag-and-drop is to manually type or paste source object references into a target field script. To add a new script on a target field, in either mapping mode or script mode, hover over the target field and click the add icon  in the upper right to open a menu of actions. From the menu select Add Script:

This opens the editable script area on the target field in script mode, where you can enter the source object reference(s) along with any other script logic. You can also drag the specific source object from the palette to the script. For a larger script area to work within, click the popout icon  in the upper right of the target field, which opens the full script editor. Once within the full script editor, click the return icon  to come back to this screen.

Mapping to a Field with an Existing Mapping

When dragging and dropping a source object to a target field that already has a mapping, you are presented with the option to copy the source object reference to your clipboard so that you can manually paste that reference into the script logic:

On clicking Continue, the target field becomes expanded with an editable script area for you to paste in the source object reference in script mode. For mappings that contain multiple references, you must then add scripting logic to make the script valid. For example:

When the editable script area is open, you can drag and drop other source objects from the palette to the script to insert the reference path directly.

You could also manually type or paste source object references into a target field script if desired. For a larger script area to work within, click the popout icon  in the upper right of the target field, which opens the full script editor. Once within the full script editor, click the return icon  to come back to this screen.

Removing a Mapping

You can remove target field mappings one at a time, or all at once for all field mappings contained within a node or all invalid field mappings contained within a node.

Remove a Single Field Mapping

To remove a single source object mapping from a target field, or unmap the field, hover over a source object within the target field and click the delete icon :

For mappings with multiple mapped objects or scripts, hover over the variable within the target field and click the edit icon , then edit the script to remove the variable mapping:

The editable script area is also accessible by clicking the script icon  on the target field.

Within the editable script area, you can also manually clear the contents of the target field script to remove the entire mapping.

Remove Multiple Field Mappings

Options for removing multiple target field mappings at once are available within a node's actions menu.

From either mapping mode or script mode, hover over a node name and click the actions menu icon  to open the actions menu. From the menu, select one of these mapping removal options:

  • Remove Loop Node and Mappings: Available only on nodes that have a loop node defined (either manually or by automatic generation), this removes the loop node definition due to mappings that are direct leaf children associated with the loop node, and removes those mappings. Any other mappings within child loop nodes beneath the parent loop node are preserved, and the node retains its loop node definition if at least one grandchild is mapped.
  • Remove All Mappings Beneath This Node: Removes all mappings on fields contained within the node, as well as all mappings on fields contained within child nodes of that node. Using this option on a root node removes all mappings in a transformation. On selecting this option, a message asks to confirm that you want to remove mappings.
  • Remove All Invalid Mappings: Removes all invalid mappings on fields contained within the node, as well as all invalid mappings on fields contained within child nodes of that node. For more information about invalid mappings, see Transformation Mapping Validity.

On This Page

Last updated:  Nov 19, 2020

  • No labels