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 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
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 am trying to migrate data from CRM on premise to CRM online.
I need to set the Ownerid value, but LCS Data Loader only seems to allow a GUID to be provided, not a lookup to the target user.
I also need to refer to users where referenced by loads of other lookups, e.g. on Activities.
The GUIDs for users will be different in CRM Online since users are auto-created by Office 365 - you can't preset the GUID to be the same as on premise.
So we need to be able to perform a lookup to the CRM Online user somehow, but I can't see how to do that in LCS Data Loader.
If this cannot be done, then there is a huge data transformation task to modify all data prior to import to substitute the old systemuserid values with the CRM Online equivalent. That is a major piece of work, easy to miss all the lookups there are in CRM to this core entity.
Hi Mike, out of the box, CRM does indeed use only GUIDs for Lookup fields such as Activities or Owner, as you mentioned. However, you can create alternate keys on these entities and which will give you the ability to set lookups that will work better for data migration scenarios.
For example, if I am attempting to import Contacts and Accounts and I want to set the Primary Contact on my Accounts, I would like to not go directly through the primarycontactid by using GUIDs. However, I could define an alternate key on my Contact entity. In this case, maybe I choose to define that the First Name and the Last Name of the Contact will make the Contact unique. Now, when I wish to set the Primary Contact on my Accounts, I can do so by mapping a column in my flat file that represents the First Name of the Contact and another column representing the Last Name.
What this would like like in the Data Loader in the mapping field drop-down would be new properties in the format of Source Field: Target Field (Key). In the example above, assuming my key was named Full Name, then the values would be "Primary Contact: First Name (Full Name)" and "Primary Contact: Last Name (Full Name)."
I hope this helps!
Business Applications communities