An OmniScript updates data from one Salesforce record, but when it completes, only some of the data is updated in Salesforce. A Data Mapper Load…

A partial data update suggests that the DataRaptor Load successfully identified the correct record but failed to update specific fields. This can happen for two primary reasons. First, if the Input JSON paths defined in the DataRaptor do not exactly match the JSON structure sent from the OmniScript (A), the DataRaptor will not find the data for the mismatched fields and will not update them. Second, the DataRaptor's DML operations respect Salesforce's security model. If the fields that are not being updated are configured as read-only for the running user (e.g., via Field-Level Security) or are formula fields (B), the update for those specific fields will fail, while other writable fields in the same transaction will be updated successfully.

C. The Preview tab in the DataRaptor is for design-time testing and simulation. The data used there, including any RecordId, does not affect the actual runtime execution from the OmniScript.

D. If the ContextId (which provides the RecordId) were misspelled, a null ID would be passed to the DataRaptor. This would cause the entire update operation to fail, preventing any data from being saved.

1. For Answer A (JSON Path Mismatch):

Source: Salesforce OmniStudio Developer Guide

Reference: In the "DataRaptor Load" section

the documentation explains the mapping process. It states

"In the Fields tab

map fields from the input JSON to fields in Salesforce objects." If the "Input JSON Path" for a field does not correspond to a path in the JSON data received from the OmniScript

no value is mapped

and thus the sObject field is not updated. (See the "Map Fields in a DataRaptor Load" subsection).

2. For Answer B (Read-Only Fields):

Source: Salesforce OmniStudio Developer Guide

Reference: The "DataRaptor Security" section clarifies that DataRaptors run in 'System Mode without sharing

' which bypasses object-level and record-sharing rules but always respects field-level security (FLS). Therefore

if a field is set to read-only for the user's profile

the DataRaptor cannot write to it

leading to a partial update.

3. For Answer D (Incorrect RecordId):

Source: Salesforce OmniStudio Developer Guide

Reference: The "Pass Data to a DataRaptor from an OmniScript" section details how ContextId is used. For an update operation

a valid sObject.Id is required. If the ID is null or invalid (as would happen with a misspelled merge code)

the DML update call fails entirely

as it cannot identify a record to act upon.