Q: 13
Universal Containers has a new custom object for Invoices that includes an Invoice Number field,
Before the Invoice object can be used, invoices will be migrated from an external system maintaining
their current Invoice Number. After the migration, salesforce will be the system of record and each
new Invoice created in Salesforce must have a unique Invoice Number.
How should the app builder configure the Invoice Number field?
Options
Discussion
Had something like this in a mock. B is the way to go since marking a Text field as unique external ID lets you import exact numbers from the old system, and prevents duplicates once Salesforce is owning the data. Makes sense, agree?
Not A, it's B. Making it a unique external ID Text field avoids issues with the migration and keeps imported invoice numbers intact. Option D's a common trap but wouldn't support keeping existing values from the old system.
Its B. Marking it as a unique external ID Text field covers the migration and future uniqueness.
Be respectful. No spam.
