12/14/16 - this is complete for the voter file importer as well.
10/26/16 Update: Addresses updated via one-time import, donation import, and membership imports are behaving as expected.
The voter file importer will be updated by the end of this week.
A technical change was made to the process of importing profiles into NationBuilder, which removed expected behavior from the process.
Importing new profiles and importing new addresses are not affected by this bug. The problem only exists when an import is expected to change an existing address.
When overwrite nonblank fields is checked, this is how address imports are currently affecting existing addresses:
- The address elements imported are replacing specific fields within the address.
- Other address fields are retained.
- Often, this leads to a new address that is mappable but has errant information in the address 2 field.
- Example: John moves from an apartment to a house
- John's home address prior to the import is 456 Broadway, Apt 2, Los Angeles, CA 91325
- Import makes John's home address 123 Main St, Apt 2, Los Angeles, CA 90066
- John's home address should be 123 Main St, Los Angeles, CA 90066
How imported addresses should behave if the overwrite nonblank fields box is checked:
- Existing address is destroyed.
- Address is replaced by elements included in the import.
Importing registered address should be handled differently to ensure that established unique identifiers are preserved.
This is how importing registered address and checking overwrite nonblank fields should should work:
- When state file ID or county file ID do not exist on a profile, importing any element of the registered address will destroy the existing address and be replaced by the import.
- If you import registered state and state file ID, and no other registered address fields, an existing profile's registered address will not be destroyed. The combination of fields will be used to establish a unique identifier that matches the imported record to an existing profile.
- If you import registered county, registered state, and county file ID, and no other registered address fields, an existing profile's registered address will not be destroyed. The combination of imported fields will be used to establish a unique identifier that matches the imported record to an existing profile.
- When state file ID exists on a profile, an import cannot update a registered address without mapping the state file ID field. An error will occur that says "signup has state file ID, must map state file ID and registered state."
- Similarly, when county file ID exists on a profile, an import cannot update a registered address without mapping the county file ID field. An error will occur that says "signup has county file ID, must map county file ID, registered county, and registered state."
Our engineers are currently working to resolve this issue. We will update this page as progress is made.
We are also working to define when the problem began, so that you have the information necessary to re-import addresses affected by this bug.