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 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
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.
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
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
Business Applications communities