Personalized Community is here!
Quickly customize your community to find the content you seek.
Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
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 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
First as it is my first post here, I would like to start by thanking you, the community, in advance for all your futur help, and I hope being able to help some of you as well.
I have an enquiry regarding the best practice to centralise the customerID from various different systems such as ERP, various Magento, Partner sites, Extranet, POS, Social and etc ? (i could easily end up with 30 foreign keys in some companies). Up to now on the previous CRM i was managing, I was implementing a Table called [ContactUniqueKeys] with a composite primary key [SystemCode,SystemContactID] composed of the unique identifier for the system and the Primary key of the contact of the named system.I know that another solution is to propagate the unique CRMID into the other systems, but i found personally that it is sometimes challenging and not possible (EDI with partner for example).
I wanted to hear your opinion on what is the best practice nowadays?
Thank you Guys, SooS
How do you plan ti migrate those information? If i were you, i'd use a tool like kingsway soft and in case of a First migration(the record are not currently in the System) that's what i would do:
I you already have those record in your dynamics, create a new field (hidden) and store the sourceId right there and use that field and the optionset as a alternate Key.
Hope It Helps!
Hi @SooS ,
Any news? Did you decide to go ahead with it ?
If you found the answer helpful for you or other readers, please mark as Verified.
Business Applications communities