Skip to main content

Notifications

Announcements

No record found.

Customer experience | Sales, Customer Insights,...
Suggested answer

Importing Accounts to update a single custom lookup field failing 100%

Posted on by 40

Hi,

I have problem to update around 900 Account records to update only one custom lookup field. The reference record in the looked up entity is already created and existing.

They all throwing the errors:

  • You cannot import data to this record because the record was updated in Microsoft Dynamics CRM
  • A duplicate lookup reference was found

I tried to manually update some account records with the same value for the lookup field I want to import, no issue.

  • david.abax Profile Picture
    david.abax 40 on at
    RE: Importing Accounts to update a single custom lookup field failing 100%

    Thanks for the reply.

    Yes, the 99% of the failures were the error message regarding the duplicate lookup.

    My issue is that,

    • Account entity there is a field "Primary Payment Term" and it should lookup to the Payment Term record
    • Every Account should have their own Payment Term record, so every Payment Term record in the entity is unique and have a reference to the account
    • All Payment term records are already existing with the Account look up in the Payment term entity

    So we have for example 100 payment term records, with the same "Name" in Payment term entity.

  • Suggested answer
    Timothy Bohte Profile Picture
    Timothy Bohte 2 on at
    RE: Importing Accounts to update a single custom lookup field failing 100%

    If someone else updates the record you're trying to import between the moment you exported the list and you import the updated list, you get the first error. Avoid this by doing your update as fast as possible and when the least people are using Dynamics.

    If you try to update a lookup field that exists multiple times with the same name, you'll get the second error. Make sure the lookup records have different names before you import the records. Otherwise look for an unique identifier field for the lookup record and use that field instead for the name of the look up to import the records.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans