Data conflicts
When matching constituents have different names or contact information, we call these "conflicts." The program compares data in these fields to find conflicts and then applies constituent update rules to resolve the differences:
-
Birth dates: Birth date field
-
Phone numbers: Number or Phone type fields
-
Email address: Email address or Email type fields
For names and addresses, the program first checks these core name and address fields for conflicts:
-
Names: First name, Middle name, Last name, Title, and Suffix fields
-
Addresses: Address type, Street number, Street name, City, State, Zip code, Is primary? and End date fields.
Then, the program checks all other additional name and address fields on the constituent record.
Automatic updates: If there are no conflicts in the core fields, the program updates them and then checks for conflicts in all additional name and address fields. If there are no conflicts in the additional fields, the program updates those as well. If there are conflicts in the additional fields, but not in the core fields, the program updates the additional fields unless the constituent update rule is set to Ignore name/address. In that case, the program does not add or update the additional fields. If there are conflicts in the core fields, the program uses the selected constituent update rule for all fields (core and additional).
Manual Review: If there are conflicts in the core fields, the program uses the selected constituent update rule for all fields (core and additional) except when the rule is set to Ignore name/address. In that case, the program does not add or update the additional fields.
If the existing constituent has a value for a field that is blank on the incoming constituent, the program does not overwrite the existing value to make it blank.
A blank value is not considered a conflict. When the incoming record includes values for fields that are blank on the existing record, the program adds the new values to the existing constituent if there are no conflicts in the other address or name fields. regardless of which constituent update rule is selected. For example, in the table below, the blank apartment number is updated because there are no conflicts between the address fields. This update occurs even if the rule is set to Add as new address, Ignore address, or Require manual review.
Incoming | Existing | Final |
---|---|---|
5 Main St. |
5 Main St. |
5 Main St. |
Apt. 5 | blank | Apt. 5 |
Boston |
Boston |
Boston |
MA |
MA |
MA |
11111 |
11111 |
11111 |
The program treats address and name fields as blocks. If there is a conflict in one address or name field, the program applies the constituent update rule to all fields in the address or name block, including blank fields. For example, in the table below, there is a conflict between the Street fields. If the constituent update rules are set to Update existing address, the program updates the blank Apartment number field because it must update the Street field.
Incoming | Existing | Final |
---|---|---|
12 Main St. | 5 Main St. | 12 Main St. |
Apt. 5 | blank | Apt. 5 |
Boston |
Boston |
Boston |
MA |
MA |
MA |
11111 |
11111 |
11111 |
The table below demonstrates what happens with the same records when the constituent update rules are set to Ignore address. In this case, the program keeps the existing values for Street and Apartment number. The blank value is not updated.
Incoming | Existing | Final |
---|---|---|
12 Main St. | 5 Main St. | 5 Main St. |
Apt. 5 | blank | blank |
Boston |
Boston |
Boston |
MA |
MA |
MA |
11111 |
11111 |
11111 |