Duplicate lookup reference error when no duplicate exists

(0) Share

Report

Posted on by Community Member

I am getting an error when importing data and have checked everything I can think of and cannot seem to find a reason. I can enter them manually but wanted to understand why I was receiving the error for future reference. See screenshot below.

I have checked to ensure that none of the Contacts have Duplicates that are Active or Inactive as well as tried disabling duplicate detection rules all around.... Any ideas??

*This post is locked for comments

I have the same question (0)

All responses (10)

Answers (0)

Community Member on at

Like (0)

Report

Sorry here is the screenshot

Was this reply helpful? Yes No
Suggested answer

Nithya Gopinath 17,078 on at

Like (0)

Report

Hi Rebecca,

Please refer the following community thread.

community.dynamics.com/.../209909

It gives you solution to this issue.

Hope this helps.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hello Nithya - Thank you for the response, I did read through that thread but the weird part is that I have double checked and do not find any duplicate lookups in which my import is referring to. The Contacts are not duplicates, I even checked inactive records to ensure there were no duplicates there :(

Was this reply helpful? Yes No
Suggested answer

Gary Letter 1,267 on at

Like (0)

Report

Hi Rebecca,

Try removing the values in ALL the lookup fields on the Contacts throwing the error and re-importing them. If the Contacts import, then that indicates that it is indeed a lookup error of the type that Nithya referenced. Then populate the lookup fields one at a time, and test the import again for each field. That should narrow it down to which lookup field is causing the error, and then perhaps you can find the duplicate record(s).

At the risk of being redundant, this is my standard explanation: "A duplicate lookup reference was found" indicates that one of the lookup field values in your import data matched more than one existing record, so CRM didn't know which one to choose. For example, if the Contact "Dave Smith" has "Microsoft" in the Company Name field, and there is more than one existing Account named "Microsoft", the record import fails. It's not that there is another Dave Smith; rather, it is that there are duplicate "Microsoft" Accounts.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Is there a workflow written on create of this record which has an output parameter? Looks like a custom workflow issue to me.

Was this reply helpful? Yes No
Wendel 105 on at

Like (0)

Report

Did you ever find out what the problem was? I am experiencing the same problem and am even receiving this error when I am refferring to a lookup record that does not even exist!

Was this reply helpful? Yes No
Suggested answer

Charles Abi Khirs 3,569 on at

Like (0)

Report

Hello,

Make sure which lookup field you are referring (maybe it is other than the one you are testing).

I experienced the same issue and found out that some of the records that I was trying to import are referencing lookup fields that have duplicated records.

What you can do is

1. Check the record that is failing

2. Take the lookup field(s) values from your Excel file

3. Search for the value of the lookup field(s) in CRM

4. You will have multiple records for the same value

Therefore, you have to make sure that the data is clean in CRM or your Excel File is not appropriate.

Was this reply helpful? Yes No
Wendel 105 on at

Like (0)

Report

There were no multiple records with te same value. Even if I used a completely random value that did not exist it would give me the duplicate lookup reference error. In the end I added another lookup field referencing the same entity. I would then enter the same value for both fields in the import file. It would fail for the old field and pass for the new, so in the end I kept the new field and got rid of the old one.

Was this reply helpful? Yes No
Suggested answer

Wendel 105 on at

Like (0)

Report

I finally found what was causing this: beside the lookup field that I was having trouble with there was a single-line-of-text field with the same display name. This caused the duplicate lookup reference error, even for values that did not exist at all! After changing the display name of the text field the problem disappeared.

Was this reply helpful? Yes No
Suggested answer

Maxbyte 5 on at

Like (0)

Report

Thanks, it will works for me

Was this reply helpful? Yes No