---
schema_version: "1"
id: a27b187774881a3b6aabc0ac96801f6b3102927f793ebdddae36ff228886e656
title: Omnistudio Data Mapper Post Action for Integration Procedures (Managed Package)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_dataraptor_post_action_for_integration_procedures.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_dataraptor_post_action_for_integration_procedures.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 73800cb6409b7e2961814aaa434661a264cc49b9b2d010aed01084a9519c9b47
description: For the managed package runtime, the Data Mapper Post Action calls a Data Mapper Load (post) to write data to Salesforce.
products:
  - Omnistudio
release: "264"
---
# 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.

![Managed Package app icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/resources-global/_corporate/images/managedpackageicon.png) This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see [Omnistudio Help](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_standard.htm&language=en_US).

For Integration Procedure examples that include at least one Data Mapper Post Action, see [Process Arrays Using Loop Blocks (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_process_arrays_using_loop_blocks.htm&release=264.0.0&type=5 "For the managed package runtime, a Loop Block iterates over the items in a data array, enabling the Actions within it to repeat for each item. For example, in ​Salesforce Industries Communications, Media, and Energy, without a Loop Block, adding four products to a cart would require running four separate Remote Actions. But one Remote Action within a Loop Block can add all four products.") and [Handle Errors Using Try-Catch Blocks (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_handle_errors_using_try_catch_blocks.htm&release=264.0.0&type=5 "For the managed package runtime, a Try-Catch Block lets you \"try\" running the steps inside it and then \"catch\" the error if a step fails.").

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)](https://help.salesforce.com/s/articleView?id=xcloud.os_dataraptor_post_action_properties_for_integration_procedures.htm&release=264.0.0&type=5)**  
    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.