How does a DataRaptor Load write data, and where can it write it?

How does a DataRaptor Load write data, and where can it write it?

• A. It writes data by updating only existing records with no field mapping.
• B. It writes data into external systems via REST calls only.
• C. It writes data into Salesforce objects by mapping input fields to target fields.
• D. It writes data to in-memory variables only.

Answer: (C)

DataRaptor Load is about taking structured input data and persisting it by mapping each input field to a corresponding field on the target object. In OmniStudio, that target is typically Salesforce objects, so the mapping defines which source values go into which Salesforce fields, enabling create, update, or upsert operations (often using an external ID for upserts). This is what allows writing data into Salesforce records directly. It isn’t about writing only to in-memory variables or limited to REST calls to external systems—the core action is writing into Salesforce objects through the defined field mappings.

DataRaptor Load is about taking structured input data and persisting it by mapping each input field to a corresponding field on the target object. In OmniStudio, that target is typically Salesforce objects, so the mapping defines which source values go into which Salesforce fields, enabling create, update, or upsert operations (often using an external ID for upserts). This is what allows writing data into Salesforce records directly. It isn’t about writing only to in-memory variables or limited to REST calls to external systems—the core action is writing into Salesforce objects through the defined field mappings.