Dedupe - Options: Non-Master Objects
What happens to fields where a unique value is required that are filled with a unique value when choosing the option to retain non-master records with a prefix?
The merge will complete, the subordinate record will be deleted, and DemandTools will report an error and the ID of the deleted record: "UnDelete,0014000000ZZVq0AAH,,,, "Message: a custom uniqueness constraint would be violated by the proposed operation Status code: 321"
Olivia M.J. Hinkle
Product Adoption Manager
Thanks, this makes sense. To make this work, we'll remove the uniqueness requirement temporarily during the merge process, and change the values in the subordinate records after completion of the merge.