Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I'm transferring some data from an older system to our dynamics CRM, i'm using the CVS import functionality for this.
But, when importing I get the error "A duplicate lookup reference was found", which is quite clear. But, I need those duplicates for other technical reasons.
Let me clarify my tables a bit.
I have three tables Project, Item and HourBooking. A project can have zero or more items and an hourBooking requires a reference to a project and one of it's items. All of the projects share the same basic item, lets call it "item 0". Currently there are about 50+ instances of this "item 0" in my system, all with a different ID.
So, I guess that's where the "A duplicate lookup reference was found" message comes from, because it doesn't know which instance of "item 0" i reference in my hour bookings.
I Hope i'm clear, but i can understand if you don't understand something about my question. Please let me know if I can clarify something :)
as you figured out, the system is given you that error because the name field has multiple hits when it tries to resolve it.
Best you do is either export the 'item 0' and use a vlookup to fill in the GUIDS rather than the name field. On the import mapping, change it to ID instead of Name field.
OR (will be easier in my opinion), add a counter field to your entity and use that value as lookup.
(OR rename all your Item 0 records with something unique just for your import and when done, rename it by export/reimport)
Thanks for you reply Wouter, I guess the easiest way of fixing this problem is to give each item a unique name. They are temporary anyways, so it won't be a problem.
Having a unique property per record, be it the name or another field is indeed the way to go if you use excel for import.
Business Applications communities