web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

The lookup reference could not be resolved

(0) ShareShare
ReportReport
Posted on by 565

Hi,

I want to import records (appointments), the entity has lookup fields (contact, account and lead).

I have sommes records have the same name e.g (Lead=Exemple1 account=Exemple1), when i try to import the CSV file, i got this error message:
The lookup reference could not be resolved.

*This post is locked for comments

I have the same question (0)
  • David Jennaway Profile Picture
    14,065 on at

    Just to clarify, do you have custom lookup fields on the appointment for each entity type, or a custom customer field, or are you just using the system fields ?

    With the data import, a lookup field can only be resolved if there is a unique record to match it to

  • Aric Levin - MVP Profile Picture
    30,190 Moderator on at

    What field are you using to the lookup? Regarding Object Id?

    If that is the case, the values must be unique or the system will not recognize it during import.

    If you have separate lookup fields for account, contact and lead (which I don't think is the case), you should not have a problem.

    Hope this helps.

  • Suggested answer
    gdas Profile Picture
    50,091 Moderator on at

    Hi,

    When you are trying to import related record and if you are not maintain order of the reference data import  then its obvious that reference will not found when its dependent on other lookup or records.

    For example if you are trying import a contact with country United Sates and the country United Sates  does not  exists in the CRM then Dynamics CRM will not create country first and then the contact. So in that case you have to import country data first and then contact with respective country. Exactly same thing happening here in your scenario.

    So ideally when you are importing any related data , need to make sure the related lookup is exists in the database.

    Hope this helps.

  • Philj Profile Picture
    4 on at

    Hi,

    I am having the same issue and I understand what you are saying however if you can't tell what the source field is that's giving the error how do you know what to import into Dynamics?

    Sorry I may just be missing something here but getting very confused

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans