Answers.Body: <p>I had the same outcome when I imported external ID, first, last name and a physical address update. My dedupe rule only contained 'external ID'. When I removed the first and last name the import worked.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-09-09T14:43:59.607Z
Answers.LastActivityDate: 2019-09-09T14:43:59.607Z
Answers.UserDisplayName: Andy Burns
Body: <p>I'm getting some (maybe 5%) email address imports rejected with the message "Matching this contact based on the de-dupe rule would cause an external ID conflict" The email addresses in question can be updated in the UI without a problem, and I can't see that adding these rejected email addresses could cause any conflict. The supervised dedupe rule is 'Name and email'. What's the cause of this error? (Changing the dedupe rule to bypass the problem doesn't work so I'm thinking this might be a bug) Civi is at 5.11.0. </p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-05-14T21:23:15.960Z
Comments.Text: Andy - I can't spot that you stated the obvious, so i will ask, does your 'import' of emails contain a field for External ID?
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-05-14T21:24:22.753Z
Comments.Text: Yes it does, should have said.
Comments.UserDisplayName: Andy Clark
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-05-15T04:18:50.193Z
Comments.Text: can you set up a dedupe rule for External ID and use that instead? i don't quite follow what is happening tbh since if you are importing External ID then that is the field it should be matching on, and it should not be overridden by a dedupe rule imo
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-05-15T12:01:34.293Z
Comments.Text: I added an External ID dedupe rule but same result. Looking at 8 examples, 7 of them were adding a home email address when there was already a main email - perhaps this is a clue. I set 'No duplicate checking' and retried - and all were rejected as duplicates!  Something wrong here...But all these emails can be added without a problem using the UI.
Comments.UserDisplayName: Andy Clark
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-06-11T14:43:23.397Z
Comments.Text: I get this as well with an external ID dedupe rule, seems like a bug.
Comments.UserDisplayName: Andy Burns
Tags: <import><duplicate-contacts>
Title: What causes this error on importing email addresses?
ThreadText: # What causes this error on importing email addresses?
  
  (Asked by: username_0 on 2019-05-14)
  
  I'm getting some (maybe 5%) email address imports rejected with the message "Matching this contact based on the de-dupe rule would cause an external ID conflict" The email addresses in question can be updated in the UI without a problem, and I can't see that adding these rejected email addresses could cause any conflict. The supervised dedupe rule is 'Name and email'. What's the cause of this error? (Changing the dedupe rule to bypass the problem doesn't work so I'm thinking this might be a bug) Civi is at 5.11.0.
  
  **Tags:** import, duplicate-contacts
  
  > **Comments:**
  > **username_1**: username_0 - I can't spot that you stated the obvious, so i will ask, does your 'import' of emails contain a field for External ID?  
  > **username_0**: Yes it does, should have said.  
  > **username_1**: can you set up a dedupe rule for External ID and use that instead? i don't quite follow what is happening tbh since if you are importing External ID then that is the field it should be matching on, and it should not be overridden by a dedupe rule imo  
  > **username_0**: I added an External ID dedupe rule but same result. Looking at 8 examples, 7 of them were adding a home email address when there was already a main email - perhaps this is a clue. I set 'No duplicate checking' and retried - and all were rejected as duplicates!  Something wrong here...But all these emails can be added without a problem using the UI.  
  > **username_2**: I get this as well with an external ID dedupe rule, seems like a bug.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2019-09-09. Score: 1
  
  I had the same outcome when I imported external ID, first, last name and a physical address update. My dedupe rule only contained 'external ID'. When I removed the first and last name the import worked.
  
  
  ---
  
  