Mapping Fields for Post, Publish, Copy, or Subtask Transitions

You can map fields in the originating item to fields in the newly created item for Post, Subtask, Publish, and Copy transitions.

Each transition type has default mappings that are used if you have not applied additional field mappings. Once you do this, the default mapping no longer applies and you must manually map to fields, such as Submitter or Title.

The following table describes mapping rules for the different transition types.

Transition Type	Default Mapping	Notes
Post Subtask Publish	Items posted within the same primary table contain all the fields values of the original items, except for the Submitter and Submit Date/Time fields. Items posted across tables contain the Title and Description of the original item.	You can map to compatible fields types.
Copy	All field values are copied from the source item to the new item, except for the Submit Date/Time and Item ID fields.	You can map to compatible fields types.

The following table lists compatible field mappings.

Source field type	Allowed receiving field type
Binary/Trinary	Binary/Trinary or Text
Date/Time	Date/Time or Text
File	File
Folder	Folder or Text
Multi-Group	Multi-Group or Text
Multi-Relational	Multi-Relational or Text
Multi-Selection	Multi-Selection or Text
Multi-User	Multi-User or Text
Numeric	Numeric or Text
Single Relational	Single Relational or Text
Single Selection	Single Selection or Text
Sub-Relational	Text
Summation	N/A
Text	Text
URL	URL
User	User or Text

Consider the following information when you apply field mapping:

Selections for Single Selection, Multi-Selection, Multi-User, and Multi-Group fields should have identical names when mapped. If a selection is not available for the field, None is selected as the value in the posted item. If a selection has been disabled or deleted, Disabled is displayed, and users must select a valid value before completing the transition.
Default values for Single Selection, Multi-Selection, Multi-User, and Multi-Group fields in the receiving project or table are overwritten by values from the source item. For example, a Post transition is used to post items from the Issues table to the Incidents table, and the Issue Type field is mapped to the Incident Type field, which has a default value of Problem Report. If a user selects Bug Report for the Issue Type field before posting an item from the Issues table to the Incidents table, the Problem Report default value is ignored and is replaced by Bug Report.
When you map Text fields, verify that the Enable Rich Text option is consistently set for both fields. For example, if rich text editing is enabled on the originating Text field, it must be enabled on the destination Text field. If not, posted text will not be rendered.
When mapping fields for Publish transitions, the mapping applies only to the Problems table, not to the Resolutions table.

To map fields when you edit a workflow in which a Post, Publish, Copy, or Subtask transition exists:

In App Explorer, select the workflow that contains the transition for which you want to map fields.
In the workflow editor, select the transition.
On the Post Options tab of the transition Property Editor, scroll down to the Mapping area.
Under This item's field, select the field to be mapped to a field in another project or table, or to a field in a new item that uses the same table.
Under Mapped to in the same row, use the drop-down list to select the field you want to map to (from the fields in the table you are posting to).
Tip: To map all fields with the same name and type, click Map Matching Fields. You can then change the mappings for individual fields as needed. If you change your mind, click Clear Mappings.

For field mapping details, refer to Post Options Tab of the Transition Property Editor.

Mapping Fields for Post, Publish, Copy, or Subtask Transitions

Related Topics