Error: You cannot assign an end date to an address that is the primary address for either the household or another member in the household. Please review the addresses and either remove the end date or uncheck the 'Update household address' checkbox.

In Import, when using any Constituent Update Batch, besides the System Generated CUB, one may notice the Update Household Address field remains blank despite the import file having a 'Yes', 'True', or '1' in the field. This can lead to one encountering the following error upon commitment when the checkbox isn't manually checked in the batch:

 

You cannot assign an end date to an address that is the primary address for either the household or another member in the household. Please review the addresses and either remove the end date or uncheck the 'Update household address' checkbox.

We are currently evaluating this issue for a fix in a future service pack.

Steps to Duplicate

1. Create a new constituent and add an address to the constituent's record. Create a household for the constituent.

2. Navigate to Administration > Import and click Generate import header file under Tasks. Select the user-defined Constituent Update Batch template in question.

3. In your newly-generated header file, fill in the constituent fields with the information from your constituent in step 1. In the address fields, enter a new address to update the address currently on the constituent's record. In the "Update Household Address" field, enter 'Yes', '1', or 'True'. Save the file.

4. Create a new import with the CUB template and select the local file you've just saved in step 3.

5. Auto-map the constituent fields and Auto-map the address fields. Save the import.

6. Start the import. When a batch has been created, open the batch and click the drop-down on the Address fields. See that the newly imported address does not have the "Update Household Address" checkbox checked. If the batch is committed without this checkbox being checked, the error is thrown. If you check it and commit, it processes as expected.

Environment

 Blackbaud CRM
 4.0
 4.0.170

Was this article helpful?