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) / The Consequences of Ha...
Microsoft Dynamics CRM (Archived)

The Consequences of Having Many Custom Entities in Dynamics 365

(0) ShareShare
ReportReport
Posted on by Kingfish 15

What are the consequences of having many custom entities in Dynamics 365 on-premise ? Should we implement our solutions with as few entities as we can or not ?

For example: I can implement two functionalities in one entity and also I can implement them in two separate entities. What's  the accurate solution for adding custom entities ? thanks.

*This post is locked for comments

I have the same question (0)
  • Verified answer
    David Jennaway Profile Picture
    David Jennaway 14,065 on at

    There are no performance issues or limits on the number of entities. In general, I'd lead this based on the ease of data entry. All things being equal, asking users to create records for multiple entities (each with a different form), is not quite as effective as just using one entity, if that makes sense. That said, if you find yourself having to conditionally hide many fields on an entity, this can get over-complex, and it may be better to split this into multiple entities

  • Verified answer
    Kokulan Profile Picture
    Kokulan 18,054 on at

    On top of what David suggested, i would say you can follow most of the relational database design or data modelling principle when you are creating Custom Entities in CRM.  

    When you create an Entity in CRM, behind the scene it creates an SQL table. When you add a lookup field to an Entity, it creates a relationship 1:N.

    What would you do if you were to design as your own database, you could follow the same approach.  Try and normalise data as much as possible don't store all the data in one entity(table) but you can do some responsible de-normalization.

    You also need to take the User Requirement into account. What your end users want, when you design entities you have to keep that in mind as well. If you store all in one entity, you may not be able to provide different views and forms without doing a lot of customisation and code

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