It is not possible to mark multiple mappings with the 'Upsert' attribute.

It is not possible to mark multiple mappings with the 'Upsert' attribute.

• A. True
• B. False
• C. Depends on mapping
• D. Only in DataRaptor Designer

Answer: (B)

Upsert uses an external ID (or Salesforce Id) to decide whether to update an existing record or insert a new one. In DataRaptor mappings, you can designate more than one field as Upsert keys. This means multiple mappings can carry the Upsert attribute, so if any of those keys are present in the incoming data, OmniStudio will try to locate a matching Salesforce record and perform an update; if no match is found, it will create a new record. If more than one key is provided, the system uses the defined priority/order to pick which key to use for the lookup. So the statement is not true—the Upsert attribute can be applied to multiple mappings.

Upsert uses an external ID (or Salesforce Id) to decide whether to update an existing record or insert a new one. In DataRaptor mappings, you can designate more than one field as Upsert keys. This means multiple mappings can carry the Upsert attribute, so if any of those keys are present in the incoming data, OmniStudio will try to locate a matching Salesforce record and perform an update; if no match is found, it will create a new record. If more than one key is provided, the system uses the defined priority/order to pick which key to use for the lookup. So the statement is not true—the Upsert attribute can be applied to multiple mappings.