Importing: Updating existing records but duplicate phone issue stops import from completing

Options
Greetings all.


When importing to update existing records, I receive the exception "Validation error: a duplicate phone number and phone type exists. Remove the duplicate to save the record". 


I understand that it's kicking back because the same phone type and number already exist, and RE isn't having it. The weird thing though, is that I ran the same process last year and it allowed duplicate phone numbers of the same type to be saved. I know this because we had to find the duplicates and remove them after the import. In the business rules section, I made sure that the duplicate phone and email settings are set to 'save record anyway', but the exception error still occurs.


I have got to be missing something simple? Else this could be one of those things that will drive me nuts!


Thanks!

Comments

  • Hi, Dan. I'm very new to the import process,  but I would suggest just not including those fields in the import, unless that's the specific data you are updating, in which case, you wouldn't really want all those duplicates anyway. Just remove those fields from the spreadsheet, don't map it, or unmap it.

    Patty Gauss


    Dan Kirk
    :

    Greetings all.


    When importing to update existing records, I receive the exception "Validation error: a duplicate phone number and phone type exists. Remove the duplicate to save the record". 


    I understand that it's kicking back because the same phone type and number already exist, and RE isn't having it. The weird thing though, is that I ran the same process last year and it allowed duplicate phone numbers of the same type to be saved. I know this because we had to find the duplicates and remove them after the import. In the business rules section, I made sure that the duplicate phone and email settings are set to 'save record anyway', but the exception error still occurs.


    I have got to be missing something simple? Else this could be one of those things that will drive me nuts!


    Thanks!

     

  • Hi Dan-


    I think the only logical answer is that when you ran the same import last year you did not have the Business Rule turned on that's preventing your import from working this time. Unfortunately there's not a way to look back in time to see if that was the case, but this explanation would make the most sense.

    57dd9681e2a5ef377ae87a2a07087c20-huge-bu

     





  • Aaron Rothberg:

    Hi Dan-


    I think the only logical answer is that when you ran the same import last year you did not have the Business Rule turned on that's preventing your import from working this time. Unfortunately there's not a way to look back in time to see if that was the case, but this explanation would make the most sense.

    57dd9681e2a5ef377ae87a2a07087c20-huge-bu

     

    The other possibility is that if you upgraded to RE 7.96 this past year you may have phone type on records that did not exist last year. In any case Aaron's suggestion should work.
  • The other responses should get you where you need to go.


    I'll offer a bit of an alternate perspective that I used when we upgraded. We migrated all the phone numbers from relationship records onto constituent records, which generated a lot of duplicates. I used a long sequence of vlookups in Excel to determine exactly which phone numbers needed to be imported, to avoid adding duplicates. Similarly, using the phone import ID allows you to update phone numbers, rather than adding an additional, if that's what you want to do. Let me know if you want any additional information about the process I used.

Categories