Which two actions should prevent the duplicate order records from being created in Salesforce?

A business has a proprietary Order Management System (QMS) that creates orders from Its website and fulfills the orders. When the order Is created in the OMS, an integration also creates an order record In Salesforce and relates It to the contact as identified by the email on the order. As the order goes through different stages in the OMS, the integration also updates it in Salesforce.

The business notices that each update from the OMS creates a new order record in Salesforce.

Which two actions should prevent the duplicate order records from being created in Salesforce?
A . Use the email on the contact record as an external ID.
B . Use the order number from the OMS as an external ID.
C . Write a trigger on the Order object to delete the duplicates.
D . Ensure that the order number in the OMS is unique.

View Answer

Answer: B, D

Explanation:

To prevent duplicate Order records from being created when updates come from the OMS:

Option B: Use the order number from the OMS as an external ID.

Setting the Order Number as an External ID allows Salesforce to recognize records based on this unique identifier during upsert operations.

Option D: Ensure that the order number in the OMS is unique.

Having a unique Order Number in the OMS ensures that each order can be accurately

identified and matched in Salesforce.

Why These Actions Prevent Duplicates:

By using upsert with the External ID, the integration can update existing orders instead of creating new ones.

// Example of upsert operation using External ID upsert orderRecord Order_Number__c;

Reference: "An external ID is a custom field that has the ‘External ID’ attribute, meaning that it contains unique record identifiers from a system outside of Salesforce."

― Salesforce Help: External ID Fields Why Other Options Are Incorrect:

Option A: Using the email on the Contact record as an External ID does not prevent duplicate Orders.

Option C: Writing a trigger to delete duplicates is not proactive and adds complexity.