Omnistudio Data Mapper Post Action for Integration Procedures

The Data Mapper Post Action calls a Data Mapper Load (post) to write data to Salesforce.

For Integration Procedure examples that include at least one Data Mapper Post Action, see Work with Data and Lists and Handle Errors by Using a Try-Catch Block.

Although a Data Mapper post action primarily creates or updates sObjects, it also produces JSON output, which you can view in the Debug log on the Preview tab. This is important when subsequent Integration Procedure steps must reference the sObjects.

In the JSON response returned by a Data Mapper post, node names are appended with the sequence number of the Data Mapper step that created them. For example:

{
  "Contact_1": [{
    "Id": "0036A000002PeaAQAS",
    "LastName": "Smith",
    "UpsertSuccess": true
  }],
  "Attachment_2": [{
    "Id": "00P6A000000EJ3RUAW",
    "Name": "angular-route.min.js",
    "ParentId": "0036A000002PeaAQAS",
    "UpsertSuccess": true
  }]
}

Data Mapper Post Action output, which can be viewed in the Debug log on the Preview tab, allows other steps in the Integration Procedure to access and use the IDs and other details of the processed sObjects.

If the Data Mapper name is CreateContact, you can reference the Id of Contact_1 in the example using the merge field %CreateContact:Contact_1:Id%.

Property	Description
Data Mapper Name Data Mapper Interface (If you’re using the designer on a managed package)	Name of Data Mapper Post