Error: Data could not be saved. The INSERT statement conflicted with the CHECK constraint "CK_SEARCHCONSTITUENT_ALIASIDONALIAS". The conflict occurred in database "xxxxx", table "dbo.SEARCHCONSTITUENT". After merging two constituents.

When a constituent has an Alias on their constituent record is used in a constituent merge the following error occurs, "Error: Data could not be saved. The INSERT statement conflicted with the CHECK constraint "CK_SEARCHCONSTITUENT_ALIASIDONALIAS". The conflict occurred in database "xxx", table "dbo.SEARCHCONSTITUENT". Uncommittable transaction is detected at the end of the batch. The transaction is rolled back."
We are currently evaluating this issue for a fix in a future service pack.

Steps to Duplicate

1. Click Constituent tab
2. Click Duplicates
3. Click Merge two constituents
4. Select Source constituent 
5. Select Target constituent
6. Merge Configuration: Merge Duplicate Constituents
7. Select - Delete source constituent
8. Click Merge
9. Receive Error: Data could not be saved. The INSERT statement conflicted with the CHECK constraint "CK_SEARCHCONSTITUENT_ALIASIDONALIAS". The conflict occurred in database "xxxxx", table "dbo.SEARCHCONSTITUENT". Uncommittable transaction is detected at the end of the batch. The transaction is rolled back. 

Environment

 Blackbaud CRM
 4.0
 4.0.173

Was this article helpful?