<< Prev Question Next Question >>
Question 65/75
Universal Containers (UC) is implementing Salesforce Sales Cloud and Service Cloud. As part of their implementation, they are planning to create a new custom object (Shipments), which will have a lookup relationship to Opportunities. When creating shipment records, Salesforce users need to manually input a customer reference, which is provided by customers, and will be stored in the Customer_Reference__c text custom field. Support agents will likely use this customer reference to search for Shipment records when resolving shipping issues. UC is expecting to have around 5 million shipment records created per year. What is the recommended solution to ensure that support agents using global search and reports can quickly find shipment records?
Recent Comments (The most recent comments are at the top.)
D. Set Customer-Reference_c as an External ID (non-unique).
External ID doesn't need to be unique to fulfill the requirement: "quickly find shipment records".
Salesforce will automatically create an index on a field marked as External ID. When a Text field is marked as External ID it gets automatically indexed, so the query optimizer will check if its index can be leveraged to drive the query execution.
https://help.salesforce.com/s/articleView?id=000320036&type=1
i am quite sure "B" is correct. They key is "quickly find shipment records". On Entering the Id in the search support agents do not want to check every shipment connected to it.
ANS: D
It can be repeated so non-unique is the only choice.
Is it true?
I think ans should be Set Customer-Reference_c as an External ID (non-unique).(D)
over the long term, we have to fill shipment record with same customer reference from other opportunities..