Microsoft Dataverse is the new name for Common Data Service, or CDS, as of November 2020. The purpose of this article is to outline some very important terminology changes with regards to the new Dataverse.
The terminology changes are documented by Microsoft to have taken place in November 2020 and according to Dynamics Edge, were observed and confirmed as live around that time.
Terminology updates related to Dataverse / Common Data Service
Based on customer feedback as well as research conducted by Microsoft, the following changes have been made regarding Common Data Service.
As of November 2020 Microsoft has made a series of very important terminology changes in Dataverse to be much more intuitive and also to make this powerful platform’s usage more productive. This was formerly known as Power Platform Common Data Service, or CDS, just prior to this major terminology change. This breakthrough enables more people than ever before to identify more readily with the true power of Power Platform! The specific terminology updates are enumerated below, and Microsoft is currently in the process of rolling out the terminology changes across the entire Microsoft Power Platform spectrum of products.
- Previously: Entity / Entities
- Now known as: Table / Tables.
- Previously: Field / Fields or Attribute / Attributes
- Now this is Column or Columns
- Previously: Record / Records
- Now known as: Row / Rows
- Previously: Option Set / Option Sets / Multi select Option Sets or Picklist / Picklists
- Now known as: Choice / Choices
- Previously: Two Options
- Now, this is known as a Yes/No
Also, make sure to note that for APIs or messages in Dataverse web services or the Dataverse Web API, words like "CreateEntityRequest" or "CreateAttributeRequest" will not change to the new terminology. From docs.microsoft.com/en-us/powerapps/maker/common-data-service/data-platform-intro:
Dynamics 365 and Dataverse Applications
Dynamics 365 applications, including ones like Dynamics 365 Customer Service, Dynamics 365 Talent or Dynamics 365 Sales, also use Dataverse directly in order to secure and even store the data being used. This powerful kind of data integration in the single data store empowers you with a unique ability to build apps more rapidly and at higher quality. By using Dataverse and Power Apps directly with your core business data in Power Platform, as it is already used within Dynamics 365, you can do this without the need for any "integrations" in many cases.
You can directly construct valuable and useful apps using your Dynamics 365 data in the dataverse data storage. You can build apps quickly within Power Apps, or for scenarios that do need integration, this is made easier by using the extensible Power Platform. This
allows anyone from novice, intermediate, and professional developers to programmatically interact with metadata and data, create custom connectors, integrate with external data, and apply business logic. Some of this requires no code or low code, meaning that Microsoft Power Platform technology offers a unique opportunity that even beginners or novices can do some of these tasks!
You can manage reusable rules and business logic. There is a set of common logic and Business Rules – those already defined in your Dataverse Tables – that can be applied to apps that are created with Power Apps to ensure data consistency, regardless of how your particular users access the data or which specific app they use to do so.
Skills are interchangeable between Dynamics 365 and Power Apps. Anyone out there who may be skilled in Power Apps or Dynamics 365 can now leverage those skills across the entire Dataverse in Power Platform. You may find that whether you are creating forms, charts, tables, relationships and more, these tasks tend to be common patterns you can learn and apply across your applications related to Dataverse and Dynamics 365.