In this example the Provider has Customer Service Management installed and the Consumer does not have Customer Service Management. The provider creates a Remote Task Definition (RTD) with the Provider table field set to Case [sn_customerservice_case] and Consumer table field set to Incident [incident].
After the Provider publishes the Remote Task Definition and it gets entitled to the Consumer, the RTD syncs to the Consumer instance.
In the Consumer, we open the Provider connection record. In the Remote task definition related list, the synced Remote Task Definition indicates that the Provider table is not present in the Consumer by the Provider table field showing label [sn_customerservice_case] rather than Case [sn_customerservice_case].
After opening the Remote Task Definition, notice the source table field values of label [sn_customerservice_case] in the Inbound fields related list. The Source table for Inbound fields in the Consumer instance is the Provider table. Once again this shows that the table Case [sn_customerservice_case] does not exist in the Consumer instance.
Let’s create a transform for the inbound field mapping for State. Typically, when creating a transform in the Consumer, you would:
- Navigate to Service Exchange for Consumer > Administration > Transforms.
- Click the New button.
When creating a transform, it is necessary to select both the Provider table and the Consumer table to align with the Remote Task Definition. Because the Case [sn_customerservice_case] table is not present in the Consumer instance, it cannot be chosen when creating a transform. As shown in the screenshot, searching for the Case table in the Provider table field results in No matches found.
A different method must be used to create the transform. In the Consumer instance, navigate to the Remote Task Definition Inbound fields related list and open the State inbound field. Next, click Create Transform button.
After clicking Create Transform, the new transform record displays with Provider table, Provider field, and Consumer table pre-populated. The Provider table shows the actual table name without the label. The Provider field looks empty but holds the provider field name. Do not change values in these pre-populated fields. Update the Consumer field to the proper value which is State in this example.
Note: The first info message in the transform record describes this process of creating a transform for a table or field not available in the consumer instance.
After selecting the rest of the values for the Transform, activate the transform with the Activate button. This is a screenshot after activating the Transform.
Note: For this example, either a simple or advanced transform can be used. If simple transform is used, transform lines must be created before the transform can be activated.
After activating the Transform, it will be visible in the Transforms Inbound related list on the Inbound field of the Remote Task Definition.
