Skip to main content

When trying to merge 2 contacts (one created by Classy and the other internally) we are getting the attached errors. Has anyone seen this and been able to get a fix? I have tried to change the Account to be the same on both of the records as I read somewhere it may be that, but it did not work.

 

Error: duplicate value found: csp__Unique_Key__c duplicates value on record with id: 0034R0000465LUm

Error: Failed to merge the contacts. Error: ConMergeException:[]: duplicate value found: csp__Unique_Key__c duplicates value on record with id: 0034R0000465LU 

 

@* Sales Cloud - Best Practices *

1 respuesta
  1. 22 sept, 9:20

    Hi Katie,

    The duplicate value error you are encountering (csp__Unique_Key__c) happens because that custom field is marked as Unique (likely enforced case-insensitively or case-sensitively) in your schema settings, and both contact records currently hold conflicting or populated values that clash during the merge operation. When Salesforce attempts to merge the records into the winning record, it briefly retains or evaluates the unique keys of both records simultaneously, triggering the block.

    Here is how you can resolve and complete the merge: 

     

    1.Clear or Modify the Unique Key on the Losing Record:

    Field Modification. 

    Navigate to the losing contact record, edit the csp__Unique_Key__c field, and either clear out the value entirely or temporarily change it to a distinct placeholder string. You can verify success when saving the edited record without a duplicate value validation error. 

     

    2.Perform the Contact Merge:

    Execute Merge. 

    Return to the contact merge tool and execute the merge while selecting the correct master record. You can verify success when the merge completes without throwing the ConMergeException block. 

     

    3.Verify the Winning Record's Unique Key:

    Post-Merge Cleanup. 

    Check the winning contact record to ensure its csp__Unique_Key__c matches the correct integration ID needed by Classy. You can verify success when the integration key on the surviving record is accurate and uncorrupted.

0/9000