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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Creating my own GUID...
Microsoft Dynamics CRM (Archived)

Creating my own GUID's before inserting new records into CRM

(0) ShareShare
ReportReport
Posted on by Sam Alex 6

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.

Thanks .

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Kokulan Profile Picture
    Kokulan 18,054 on at

    Hi Sam

    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

    blogs.msdn.microsoft.com/.../the-dangers-of-guid-newguid

    I think in your SQL Column if you set it to generate Id using NEWSEQUENTIALID(), it should generate sequential GUID.

  • Suggested answer
    Dynamics365 Rocker Profile Picture
    Dynamics365 Rocker 7,755 on at

    You can create GUID and it will be imported in CRM.

    But make sure that newly generated GUID should be not in CRM.

  • David Jennaway Profile Picture
    David Jennaway 14,065 on at

    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

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

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