A customer has a new Engagement Manager who is going to be the new Primary Contact for the Account. What type of mapping does a DataRaptor Load use…

Linked Mapping is the correct feature used in a DataRaptor Load for this scenario. It enables a multi-step process within a single transaction: first, it creates a new sObject record (the Engagement Manager as a Contact), and second, it uses the Salesforce ID of that newly created record to populate a lookup field on another sObject (the Primary Contact field on the Account). This creates the new record and establishes the relationship simultaneously.

A. Relationship Query: This is a feature of DataRaptor Extracts used to query and retrieve data from related objects, not for loading or updating records.

C. Lookup Mapping: This is used to find the ID of an existing record based on a secondary key to populate a lookup field, not for creating a new record first.

D. Lookup Key: This term refers to the field used to perform a lookup (e.g., an external ID), but it is not a type of DataRaptor mapping itself.

---

1. Salesforce Help

OmniStudio Documentation: DataRaptors > Link sObjects in a DataRaptor Load. This section explicitly states

"To link sObjects

you map the ID of one sObject to a lookup field in another sObject. For example

you can create a Contact and link it to an existing Account." This directly describes the process of creating a new record and using its ID to update a related record.

2. Salesforce Trailhead: OmniStudio DataRaptors > Load Data with DataRaptors. The unit "Create Related Salesforce Records" demonstrates this concept. It explains how to map the ID of a newly created object (e.g.

Contact:Id) to a lookup field on another object (e.g.

Account:PrimaryContactc) within the same DataRaptor Load

which is the definition of Linked Mapping.