Skip to main content

Key Concepts for Microsoft Dynamics 365: Entities and Attributes

Types of Dynamics Entities
To understand Microsoft Dynamics 365 (formerly Dynamics CRM and Dynamics 365 Customer Engagement), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This is the second post in a series, and covers entities and attributes.

Entities are the most fundamental part of Dynamics 365 in terms of storing your business data.  They are similar in concept to database tables, and the relate to one another like tables in a relational database. For instance, Dynamics 365 has an entity called Contacts that stores data such as name, address, and email address of people that you track.   Accounts is a related entity that describes the organizations to which Contacts may belong.

Although they are similar to database tables, Dynamics entities allow you to do some customizations that are not possible in a standard database table.  Field labels, for instance, are part of an entity, and they may differ from the field (attribute) names.  Here is the PowerApps menu showing objects related to an entity:


Dynamics 365 has three types of entities:
  • Business entities. Entities that are included in apps such as Dynamics 365 Sales, Marketing, or Customer Service. These may be set to allow or prevent customization. 
  • Custom entities. Similar to business entities, custom entities are defined by the owner of the solution in order to extend Dynamics to meet business requirements which are not fulfilled by standard apps.  Purchasing third party apps will also add custom entities to your solution. 
  • System entities. Entities provided by Microsoft that may be edited based on the managed properties set for each entity.  You cannot customize system entities. 
Attributes are analogous to fields in a database table.  The data contained in an attribute is often entered by a user in a form which is associated with an entity.  For instance, the Contacts entity contains attributes such as first name, last name, city, state, postal code and email address.  Attributes have properties that you can configure such as the data type, field length, derivation and requiredness. 

Adding attributes to an entity is one of the most common customizations in Dynamics 365.   From the entity in PowerApps you can click the menu item to add a new field which shows this form:


Field properties contain advanced options which can be used for lookups, field help, derivations, and other functions, as shown in the Territory field of the Accounts entity.


All attributes are associated with entities. Field types such as text, option set, currency and date determine what data is allowed in each field. Your Dynamics solution is likely to have dozens of entities and hundreds of attributes. 

Understanding Dynamics 365 concepts will help you get the most from your software investment. 

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan