{"id":280,"date":"2016-11-01T05:14:09","date_gmt":"2016-11-01T12:14:09","guid":{"rendered":"https:\/\/cm-edgetun.pages.dev\/en-us\/power-platform\/blog\/power-apps\/ga-common-data-model\/"},"modified":"2025-06-11T08:16:47","modified_gmt":"2025-06-11T15:16:47","slug":"ga-common-data-model","status":"publish","type":"post","link":"https:\/\/cm-edgetun.pages.dev\/en-us\/power-platform\/blog\/power-apps\/ga-common-data-model\/","title":{"rendered":"Introducing the new entities in the Common data model (Previous version)"},"content":{"rendered":"

Note : This blog post relates to an earlier version of the Common Data Service and these templates are no longer available in the current release.<\/strong><\/p>\n

Along with the general availability of PowerApps<\/a> and the Common Data Service<\/a>, we are extremely pleased to release the first version of the standard entities. The Common data model comprises the set of standard entities deployed within every database in the Common Data Service allowing the app maker to quickly and easily build apps, as well as leverage apps from multiple sources that can use the same underlying data model.<\/p>\n

You can get an overview of the standard entities here.<\/a>
\n\"1610<\/a><\/p>\n

The standard entities included within each Common data model database are intended to be used for key organizational data that many businesses and apps would use. We will continue to introduce new standard entities in the Common Data Model based on feedback, our research and popular apps in the market. It\u2019s important for app makers to always use standard entities where possible to ensure apps from Microsoft, ISVs and other developers can all work against a common set of data. Leveraging the standard entities also means you benefit from language translations, predefined sample data, security permission sets and improvements released by Microsoft. The standard entities also include relationships to each other to support common business processes. Standard entities can always be extended with custom fields to support additional business data or support additional relationships.<\/p>\n

\"LightKeep in mind : It\u2019s important for app makers to always use standard entities where possible to ensure apps from Microsoft, ISVs and other developers can all work against a common set of data. <\/strong><\/p>\n

In this version, we\u2019ve released the following categories of entities :<\/p>\n

\n\n\n\n\n\n\n\n\n
Functional group<\/b><\/td>\nDescription<\/b><\/td>\n<\/tr>\n
Foundation<\/td>\nThe Foundation entities contain information that is relevant to nearly every other entity group. This group contains entities such as Product, Product Category, Business unit and Cost center.<\/td>\n<\/tr>\n
People, organizations, and groups<\/td>\nThese entities encompass a rich set of people and organizations that you might interact with, including Workers, Fans, Alumni, and Families.<\/td>\n<\/tr>\n
Purchase<\/td>\nThe Purchasing entities let you create purchasing solutions including Purchase orders and Vendor invoices.<\/td>\n<\/tr>\n
Sales<\/td>\nThe Sales entities let you create end-to-end sales solutions, from tracking Leads and Opportunities, to following through with Contacts, to accepting and delivering orders, to sending invoices.<\/td>\n<\/tr>\n
Customer Service<\/td>\nThis group contains entities related to Case Management to manage issues from your Account, including case tracking, escalation, and documentation.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

\u00a0<\/p>\n

With this release we have also enriched each entity with additional metadata including :<\/p>\n