Developers: Understand terminology in Microsoft Dataverse
If you are familiar with the ADO.NET Entity Framework, architects and developers of data-oriented applications have struggled with the need to achieve two different objectives.
- They must model the entities, relationships, and logic of the business problems they are solving.
- They must also work with the data services used to store and retrieve the data.
The Entity Framework enables developers to work with data in the form of domain-specific objects and properties, such as customers and customer addresses, without having to concern themselves with the underlying database tables and columns where this data is stored.
In Power Apps and Dataverse, while tables and columns are used in the user interface and refer to the general idea of how data is stored in the Dataverse database, specific terminology (such as entity and attributes) is used to refer to the underlying data model and interfaces that developers work with depending on the protocol or technology used to interact with data.
The data structures that developers work with are exposed as entities, and the term is baked in the names of things developers use. For example:
|Create a Dataverse table||Web API||POST an instance of the EntityMetadata EntityType to the
|Create a Dataverse table||.NET SDK||Create an instance of the EntityMetadata Class and use the CreateEntityRequest Class to send this to the Organization service|
|Create a row or record in a Dataverse table||Web API||POST data defined as an a specific EntityType. You can find a list of these EntityTypes here: Web API EntityType Reference|
|Create a row or record in a Dataverse table||.NET SDK||Create an instance of the Entity Class or a class that inherits from it (Account, Contact, etc.) and use the CreateRequest Class to send this to the Organization service. A developer can find the information they need to use the Entity class in the entity reference.|
Terminology use depending on protocol or technology
The terminology used in the developer documentation depends on the protocol or class library used by developers.
When working with the Web API, we use the terminology defined by the OData protocol. Data structures are defined as EntityTypes, which have properties and navigation properties.
When working with the .NET SDK, we use Entity because there is an Entity class. The Entity class has an Attributes property that contains a collection of attributes that are defined by data in an AttributeMetadata Class and many other classes derived from it.
We use the appropriate terminology to describe the SDK and Web API technology. The developer documentation will at times use different terminology than the Power Apps user interface. The table below will help guide you to some of the terminology differences between the developer documentation and rest of the Power Apps documentation.
|Power Apps UI||Dataverse SDK||Dataverse Web API|
Submit and view feedback for