The Common Data Service allows you to securely store and manage data within a set of standard and custom entities. An entity is a set of fields used to store data similarly to a table within a database. After your data is stored you can use Microsoft PowerApps to build rich applications using your data:
Each entity contains a set of records that users can create, read, update, and delete. You can create relationships between entities so that you can look up information in one entity based on a record in another entity. For example, you could create a custom entity to track events which a customer had attended. By adding the Customer to your custom entity as a lookup field, you establish a relationship between the two entities which can be leveraged in your app and in reporting.
For information on purchasing a plan for using the Common Data Service, see Pricing info.
Entities within the Common Data Service, both standard and custom, allow a secure and cloud-based storage option for your data. Entities allow you to create a business-focused definition of your data for use within your apps. If you're not sure if entities are your best option, consider these benefits:
When you develop an app, you can use standard entities, custom entities, or both. If a standard entity can serve a particular purpose in your app, you should use it rather than developing a custom entity that does the same thing. If a standard entity would serve a purpose with a few changes, you can add fields to suit your needs.
Note: If possible, use standard entities (with custom fields added, if required). This will ensure that you can benefit from new features or apps that leverage these entities in the future.
Each field has a name, display name, data type, and some simple validation. Data types include, for example, text, date, or number. Validation ensures that required fields contain data and records are unique if the entity requires them to be. Every field falls into one of three categories: system fields, standard fields, or custom fields.
All entities, whether standard or custom, are created with a set of read-only fields that you can't change, delete, or set to a value. For more information, see System and record title fields. These are the most important system fields:
Each standard entity contains a set of default fields that you can't change or delete. For a list of the entities and their fields, and a list of the picklists, see Standard entities.
You can create custom fields in either a standard entity or a custom entity. You must specify the name, display name, and data type of each custom field. For a complete list of supported types, see Entity field data types.
You can navigate between records in entities if they have a relationship that's defined as a field of the Lookup data type. To create a lookup relationship, add a field of data type Lookup in one entity, and point to the entity in which you want to look up information. For more information, see Entity relationships via lookup field.
For a list of the entities and their fields, and a list of the enumerations, see Standard entities.
|Customer Service||The Customer Service entities manage issues from your customers, including tracking, escalation, and documentation.|
|Foundation||The Foundation entities contain information that is relevant to nearly every other entity group. This group contains entities such as Address and Currency.|
|People, Organizations, and Groups||These entities encompass a rich set of people and organizations that you might interact with, including employees, contractors, donors, volunteers, fans, alumni, and families.|
|Purchasing||The Purchasing entities let you create purchasing solutions.|
|Sales||The Sales entities let you create end-to-end sales solutions, from tracking leads and opportunities, to following through with contacts, accepting and delivering orders, and sending invoices.|
With the Microsoft PowerApps common data model we collect and store custom entity and field names in our diagnostic systems. We use this knowledge to improve the common data model for our customers. The entity and field names that Creators create help us understand scenarios that are common across the Microsoft PowerApps community and ascertain gaps in the service’s standard entity coverage, such as schemas related to organizations. The data in the database tables associated with these entities is not accessed or used by Microsoft or replicated outside of the region in which the database is provisioned. Note, however, the custom entity and field names may be replicated across regions and are deleted in accordance with our data retention policies. Microsoft is committed to your privacy as described further in our Trust Center.