When attempting to commit a batch with a transaction that was submitted via BBIS, users may receive the error:
Data could not be saved. The INSERT statement conflicted with the CHECK constraint "CK_CONSTITUENT_KEYNAME". The conflict occured in database "[database ID]", table "dbo.CONSTITUENT", column 'KEYNAME'. BBERRR_ORIGINAL_ERROR:547BBERR_ORIGINAL_PROCEDURE:USP_BBNC_GETORCREATEORGANIZATIONBBERR_ORIGINAL_LINE_NUMBER:35
This check constraint message indicates that there was a conflict in the KEYNAME field (Last/Organization/Group Name). Typically when a transaction is downloaded from BBIS, the name fields are taken directly from BBIS and entered into the batch, so there are no check constraint conflicts. However, in this case, the KEYNAME value that was in the batch did not match what came from BBIS. To resolve this issue:
1. Delete the BBIS batch (do not delete the row with the check constraint - this will delete that transaction from your system entirely, whereas deleting the whole batch allows you to re-download those transactions) 2. Re-download the transactions. 3. Commit the batch.