Power Platform Community Forum Thread Details

I have read many articles talking about the useful benefits of using the Common Data Model (CDM). The main benefits I am aware of is the reduction in data silos that simplifies the integration process. I am currently designing a database using Dataverse and was wondering if using the preset CDM templates are worth using. I am hesitant on using the CDM templates because I don't see how they could be much more useful then building custom tables and the CDM templates schematic structure confuse me.

My questions are.

1. What are the main benefits of using the CDM templates?

2. Is CDM just a fad or can you see the CDM growing in popularity and functionality for the future?

Thanks!

Categories:

Microsoft Dataverse with Power Apps

with Dataverse you always have a small piece of the CDM in your structure.

Account, Contact and User (systemuser) are always there when you create a Dataverse environment.

If you have also Dynamics 365 apps (like Sales) you get also other tables that you can find inside the CDM like Lead, Opportunity, etc etc.

If you create a custom table you can try to follow the CDM structure but it will not be exactly the same.

Let's do an example with the Lead table.

If you have the Dynamics 365 Lead table you have built-in fields like Subject, Description, etc etc.

If you don't have it and you create, your fields will be prefix_Subject, prefix_Description, as your custom tables will always contain the prefix (so they will not be 100% exact CDM).

Bottom line, if you have already tables that suit your scenario and you have the app installed you can use them, otherwise you can create your own tables and if you like follow the CDM guidelines.