The Vlocity DataRaptor cannot prevent duplicates when loading data into Salesforce Objects.

The Vlocity DataRaptor cannot prevent duplicates when loading data into Salesforce Objects.

• A. True
• B. False
• C. Yes, but only in Salesforce Classic
• D. Depends on mapping

Answer: (B)

Using Upsert in a DataRaptor Load with a unique External ID lets you prevent duplicates when loading data. Salesforce checks for an existing record with the same External ID; if found, it updates that record, and if not found, it creates a new one. This means duplicates are prevented as long as the External ID uniquely identifies each record. If you use Insert instead of Upsert, duplicates can be created because there’s no matching step. The mapping itself is just how fields line up between source data and Salesforce fields, not what prevents duplicates. This behavior works in both Lightning and Classic, and it’s not dependent on mapping alone.

Using Upsert in a DataRaptor Load with a unique External ID lets you prevent duplicates when loading data. Salesforce checks for an existing record with the same External ID; if found, it updates that record, and if not found, it creates a new one. This means duplicates are prevented as long as the External ID uniquely identifies each record. If you use Insert instead of Upsert, duplicates can be created because there’s no matching step. The mapping itself is just how fields line up between source data and Salesforce fields, not what prevents duplicates. This behavior works in both Lightning and Classic, and it’s not dependent on mapping alone.