OMNISTUDIO-DEVELOPER practice question 9 of 15

A developer writes an OmniScript that includes a DataRaptor that updates the Account status based on information provided from the OmniScript. The information must be updated only if the Account record already exists. Otherwise, a new account must be created. How should the developer accomplish this task?

Full set: 86 questions
Answer options
A: Check the Upsert Key checkbox on the Account Status field
B: Check the Upsert Key and Is Required for Upsert checkboxes on the Account Id field Correct answer
C: Populate the Lookup Object and Lookup Fields
D: Check Overwrite Target For All Null Inputs checkbox on the Account Id field
Correct Answer:
B. Check the Upsert Key and Is Required for Upsert checkboxes on the Account Id field
Explanation

A DataRaptor Load performs an "upsert" operation (update existing or insert new) by using a unique identifier to match incoming data with records in Salesforce. The standard mechanism for this is to designate a field as the Upsert Key on the Fields tab of the DataRaptor. When the Account Id field is marked as the Upsert Key, the DataRaptor will search for an Account with that ID. If a match is found, it updates the record. If no ID is provided or no match is found, it creates a new Account record. This configuration directly fulfills the requirement.

Why Incorrect

A. Check the Upsert Key checkbox on the Account Status field: The Status field is not a unique identifier for an Account record; multiple accounts can have the same status. Using it as an upsert key would lead to incorrect data updates.
C. Populate the Lookup Object and Lookup Fields: This feature is used to find the ID of a related record to populate a lookup field on the target object (e.g., finding an OwnerId for the Account), not for the primary upsert logic of the Account object itself.
D. Check Overwrite Target For All Null Inputs checkbox on the Account Id field: This setting controls whether a null input value should overwrite an existing value in the database. It does not determine the core create-versus-update logic of an upsert.

References

1. Salesforce Help, OmniStudio Documentation, "Define Upserts and Relationships in DataRaptor Loads": "To configure an upsert, in a DataRaptor Load, on the Fields tab, map an input field to a Salesforce field that is either an External ID or is otherwise unique. Then select the Upsert Key checkbox for that field. When the DataRaptor runs, if a matching record is found, the DataRaptor updates it. If no matching record is found, the DataRaptor creates one." This directly supports the use of the Upsert Key checkbox as described in option B.

2. Salesforce Help, OmniStudio Documentation, "DataRaptor Load Fields Tab": This section details the properties available on the Fields tab, explicitly mentioning the Upsert Key checkbox: "Select to use the field to match existing records in an upsert." This confirms the mechanism described in the correct answer.

Scroll to Top