Error: The INSERT statement conflicted with the CHECK constraint CK_VOLUNTEER_VALIDCONSTITUENTTYPE - TA/CRM sync

When merging an account in TA, the duplicate account may end up having the below sync merge error in CRM:

(USP_MERGETASK_CONSTITUENTVOLUNTEERS,160) The INSERT statement conflicted with the CHECK constraint "CK_VOLUNTEER_VALIDCONSTITUENTTYPE". The conflict occurred in database "23695P_cd4d1fc9-53ab-499b-aefa-3035f9e418f8", table "dbo.VOLUNTEER", column 'ID'.

 
This is caused by the volunteer record being associated with a household record. This violates the CK_VOLUNTEER_VALIDCONSTITUENTTYPE constraint and it should not be possible for records like this to be in CRM. They are usually inserted by conversion or early day sync setup users.

When the merge happens, it tries to move them to the retained household record, which violates the check constraint, so you get this error.

The solution is to either move volunteer records to a new constituent that is not a household or delete the volunteer records. If you are unable to do this in CRM, contact TA Support for assistance.

Environment

 RSR

Was this article helpful?


Thanks for your feedback! Did this solve your issue?

Comments (optional):


Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):


Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.