Skip to end of metadata
Go to start of metadata


Some elements of the user interface are shared by the display modes for accessing a transformation: mapping mode, script mode, and preview mode. This page covers elements that are shared by the header of the transformation screen:

  • Mapping Mode

  • Script Mode

  • Preview Mode

Renaming a Transformation

When you create a new transformation, its default name is New Transformation. Subsequent new transformations with default names are appended with an incremented number in parentheses. Transformation names must be unique and must not contain forward slashes (/) or colons (:) to be valid.

To rename a transformation from within the transformation configuration screen, edit the Transformation Name field in the top left:

Transformations can also be renamed from these locations:

Adding Notes

You can add custom notes to a transformation that serve as documentation or reminders for yourself or project collaborators. To add a note, click the note icon next to the transformation name:

An editable area opens where you can enter the text of your note. Then click Post to add the note on the transformation:

Your posted note is displayed, along with your name and a timestamp. Anyone with edit access to the transformation can remove notes by clicking the remove icon . To close the note, simply click another part of the interface.

When one or more notes are present, the note icon color is displayed in orange:

Additional notes can be added using the same method described above.

Viewing Save Status

After making changes to a mapping, the transformation configuration saves automatically. The save status is displayed along the top of the screen next to the transformation name and note icon:

The presence of a red asterisk following the time indicates that the transformation has unsaved changes:

To manually save the transformation, use Control+S (Windows or Linux) or Command+S (macOS).

To learn more about auto-save, see Cloud Studio Permissions, Collaboration, and Saving.

Previewing a Transformation

After you have configured a transformation mapping, you can use sample data to test the transformation.

Mapping and script modes provide a Preview button to enter preview mode:

In preview mode, this button expands to interact with the data being previewed:

Returning to the Workflow

To return to the design canvas, click Return to Workflow in the top right:

The workflow that contains the open transformation is displayed.

Viewing or Editing the File Schema

After defining a schema within a transformation, menu actions for that schema are available along the top of the transformation configuration screen. Along the top of either the source or target side, click the gear icon  to open the actions menu:

Menu ItemDescription

Edit Activity opens the activity configuration for you to make changes as necessary (see Schemas Defined in an Activity). This action is available only when the transformation has an adjacent activity with a schema.

For file-based activities, you can edit the configuration to clear or swap out the file you selected to use for the file schema. For other activities, you can edit the query, change the object selection, or other such configuration. 

TIP: If you see another schema besides the schema provided by the activity in the transformation, you may have another schema defined in the transformation that is overriding the activity schema. After clearing the schema being used in the transformation (with the Clear Schema option), the schema provided by the activity is automatically inherited by the transformation.

Edit Schema opens the schema editor for you to edit the schema (see Schemas Defined in a Transformation). This action is available only for schemas that are editable.

When you edit a schema that was created from a sample file in a transformation, the configuration screen for a custom flat schema or custom hierarchical schema opens for you to add or edit fields and/or nodes as required. Schemas provided by an adjacent activity are not editable. 

On opening a schema that is referenced by multiple components, a dialog displays a list of any components that reference the schema and will be affected by any changes:

Refresh Schema regenerates the schema from the endpoint. This action is available only for schemas inherited from an adjacent server-based activity (except for Database, NetSuite, Salesforce, Salesforce Service Cloud, or ServiceMax endpoints).

This action also regenerates the schema in other locations throughout the project where the same schema is referenced, such as in an adjacent activity. For more information, see Schema Regeneration.

Clear Schema clears the current schema from the transformation. This action is available only for schemas defined within a transformation. When removing a schema, a message asks you to confirm removal of the schema, with these results:

  • Source Schema: Removal of a source schema may result in invalid mappings. For more information, see Transformation Mapping Validity.

  • Target Schema: Removal of a target schema removes all mappings.
NOTE: After clearing the schema, if an adjacent activity is providing a schema, it is automatically inherited by the transformation.

Filtering or Searching

Using filter or search can help you locate a specific field within the source or target structures. You can also use search on the source structure to locate a specific variable to use in the target structure, or you can use search on the target structure to search within transformation mapping scripts themselves.


In mapping and preview modes, the View dropdown is located at the top of both the Source and Target structures. In script mode, the View dropdown is present at the top of the Target structure. This dropdown allows you to filter by these selections:

  • All Fields: All fields are displayed.
  • Mapped: Only fields that have been mapped are displayed. In mapping and preview modes, within the Source structure, mapped objects are limited to those that have been mapped to a target field. In all modes, for the Target structure, mapped fields are those that have been defined in some way (with a source object, a variable, a custom value, or any other script logic). Mapped fields show a script icon  in the upper right of the target field.
  • Unmapped: Only fields that have not been mapped are displayed.
  • Invalid: This option is available only on the Target structure. Only fields that have been mapped where the mapping is not valid are displayed. Mapping validity is detailed under Transformation Mapping Validity.
  • Required: This option is available only on the Target structure. Only fields that have a cardinality key of [1] or [1+] are displayed. For more information, see Cardinality Key under Nodes and Fields.

In mapping and preview modes, when viewing mapped objects within the Source or Variables tabs, a number in parentheses and the color orange indicates the number of times that each object is referenced on the target side of the transformation.

In addition, on hovering over a source object, line(s) appear that connect the source field to any target fields it is mapped to or nodes it is referenced within. Click directly on the number to display the referenced target field(s) or node(s) and click to automatically scroll to the object or node in the target structure.

When viewing mapped objects within the Target structure, on hovering over the field a line appears that connects the mapped target field to its origins in the Source or Variables tabs, if applicable. Click the mapped source object to automatically go to the object in the tab.

Clicking the name of a mapped target object collapses it so that its mapped objects are not visible.

If a collapsed node contains target field mappings, that node is shown in bold to indicate it contains mappings:


You can also search for specific fields in all modes. A search icon  is located at the top of the Source and Variables tabs in mapping and preview modes, and the Target structure for all modes. Click this icon to open a search box where you can enter a keyword or multiple keywords separated by commas.

When searching on the source structure, fields or variables that have any of part of any of the keywords in their name are returned.

When searching on the target structure, fields that have any part of any of the keywords in the field name or within a field's transformation mapping script are returned.

NOTE: Within the Source tab and the Target structure, the search is limited to the selected filter. To search both mapped and unmapped fields, make sure to select All Fields in the filter dropdown.

  • No labels