When to Use Omnistudio Data Mappers and Integration Procedures

Omnistudio Data Mappers read or write Salesforce SObject data or perform single-step data structure transformations. Omnistudio Integration Procedures can interact with many types of data, including REST APIs and Apex classes, and process it in multiple steps. For some use cases, a single Data Mapper is sufficient. Integration Procedures usually call one or more Data Mappers and are more flexible and powerful. Use these guidelines to help you determine which to build.

Use a single Data Mapper if:

• You read data from SObjects or write data to SObjects, but not both.

• The SObjects you read from or write to have a defined relationship. For example, Accounts and Contacts have a relationship because a Contact can have an AccountId value.

• You only have to work with JSON or XML data. No SObjects are involved.

• You can perform any needed filtering, calculation, or reformatting of data values using one or a series of formulas.

• You can make any needed changes to the data structure by mapping input JSON nodes to output JSON nodes.

• You don't read from or write to CSV files, Apex classes, REST APIs, or external objects.

• You don't send email, merge lists, or handle errors.

Use an Integration Procedure if:

• You must both read from and write to one or more SObjects, which means you must call at least two Data Mappers.

• The SObjects you read from or write to have no defined relationship.

• Transforming your data can't be done using formulas alone. For example, different conditions determine whether some filtering or calculations are performed at all.

• JSON node mappings aren't straightforward or require a series of steps.

• You read from or write to multiple data source types, such as SObjects, CSV files, external objects, Apex classes, or REST APIs.

• You perform actions such as sending emails, merging lists, or handling errors.