Omnistudio Data Mapper Post Action for Integration Procedures (Managed Package)

For the managed package runtime, the Data Mapper Post Action calls a Data Mapper Load (post) to write data to Salesforce.

This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.

For Integration Procedure examples that include at least one Data Mapper Post Action, see Process Arrays Using Loop Blocks (Managed Package) and Handle Errors Using Try-Catch Blocks (Managed Package).

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 need to 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
  }]
}

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%.

• Omnistudio Data Mapper Post Action Properties for Integration Procedures (Managed Package)
  For the managed package runtime, these properties are unique to or function in a unique manner in Data Mapper Post Actions. The Data Mapper Post Action calls a Data Mapper Load (post) to write data to Salesforce.