Data Mapper Execution (POST)

Execute a data mapper from Apex classes by specifying the name of the data mapper along with additional inputs and options.

When using the Data Mapper (DM) Connect API, HTTP callouts cannot be executed in the same transaction. This is because these APIs perform an implicit DML operation through the underlying Connect API framework. If a callout is required, it must be executed in a separate transaction, for example by using an asynchronous mechanism such as @future.

Note

Resource

1/connect/omni-global/data-mapper/execute/name

Resource example

1https://yourInstance.salesforce.com/services/data/v66.0/connect/omni-global/data-mapper/execute/Get Account Details

Available version

64.0

HTTP methods

POST

Path parameter for POST

Parameter Name	Type	Description	Required or Optional	Available Version
`name`	String	Name of the data mapper.	Required	64.0

Request body for POST

JSON example

1{
2  "dataMapperInput": {
3    "inputs": [
4      {
5        "Name": "Get Account Details"
6      }
7    ]
8  },
9  "inputType": "JSON",
10  "options": {
11    "ignoreCache": false
12  }
13}

Properties

Name	Type	Description	Required or Optional	Available Version
`dataMapperInput`	Data Mapper Execute Input Data	Details for executing the data mapper.	Required	64.0
`inputType`	String	Type of data mapper input. For example, JSON, XML, or custom class.	Required	64.0
`options`	Data Mapper Execution Options	Optional parameters to refine the data mapper execution.	Optional	64.0

Response body for POST

Data Mapper Execution Details

Public Sector Solutions Developer Guide

Data Mapper Execution (POST)