Connect and collaborate with fellow Blackbaud users.
Error 1: The message “Data could not be saved. The UPDATE statement conflicted with the FOREIGN Key constraint" seems to appear anytime you have selected a constituent that has a pre-existing invalid address on its record after you choose to validate the addresses, and choose a valid address returned by QAS. The batch then allows you to validate and commit without a problem. It also successfully updates the record with the new address that we selected, but received the error message on. So it seems to be a validation error that doesn’t actually prevent successful commit of a QAS returned address, but is confusing for an end user.
Error Message: “Data could not be saved. The UPDATE statement conflicted with the FOREIGN KEY constraint "FK_BATCHCONSTITUENTUPDATEADDRESSES_COUNTYCODEID". The conflict occurred in database "41721S_485229e0-9a3e-4d9b-abdf-460521e47959", table "dbo.COUNTYCODE", column 'ID'’.
Error 2: The message “An error occurred while attempting to validate the batch of addresses. A table entry description length must be between 1 and 100 character” appears after clicking “Validate addresses (all rows)”. We are not sure what the trigger is at this point. Furthermore, in testing, some records produce the error sometimes, and 5 minutes later do not produce the error.
The second error is more serious as its cause is unknown, and it is frequently preventing use of address validation on the CUB batches as a whole. You can commit the CUB batch, but wouldn’t be able to use address validation which is a large component of updating constituents.