Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
I have to batch load lots of records into CRM which will be linked between entities where I'm creating the parent and children records. Is there any issue with me creating the GUID's in MS SQL first in our staging data then when importing setting the GUID in CRM when the record is created? This will save so much time compared to having SSIS components running in tandem to create the parent then pass the GUID to the child to create it and so forth. I'll use newid() in MS SQL to create these.
Yes you can generate GUID and set them when you create records, I have done this in few projects.
One thing to note if you are creating loads of records in bulk, better to generate sequential GUID to make sure your create operation performs well.
Please follow the link to know more about what happens if the GUID generated is not sequential
I think in your SQL Column if you set it to generate Id using NEWSEQUENTIALID(), it should generate sequential GUID.
You can create GUID and it will be imported in CRM.
But make sure that newly generated GUID should be not in CRM.
As per the previous posts, the only impact of defining your own Guids would be a possible SQL performance hit at the CRM end when creating the records, which you can mitigate by using NEWSEQUENTIALID. In practise, this overhead is normally minor compared to the latency of sending the create requests, though if you're inserting data into entities that are in heavy use (and especially if you have plugins on the entities), then you could theoretically cause SQL locking issues
Business Applications communities