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

PowerApps Portal: The Successor to Microsoft Dynamics Portal

In case you have been reviewing Microsoft's new pricing for its Dynamics products which was released this month and have been unable to find Dynamics Portal, it has been rebranded as PowerApps Portal and shifted to the PowerApps side of the Microsoft product family.


Rebranding the portal product underscores the importance of app scenarios involving external users such as customers and suppliers.  It also provides a simpler interface than Dynamics 365 for occasional users.

The new portal pricing is based on the number of unique users who log into the portal each month (for authenticated users) and on the number of page views for anonymous users.  "A login provides an external authenticated user access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Internal users can be licensed either by the PowerApps per app or per users plans, or a qualifying Dynamics 365 subscription."

Pricing starts at $200/mo. for 100 dail…

ScreenMeet Remote Support Tool for Dynamics 365 Customer Service

I met Lou Guercia when he was president and CEO of Scribe Software, the leading CRM integration tool.  Scribe was acquired by TIBCO Software in 2018.  I recently reconnected with Lou and learned about ScreenMeet, the company he joined as chief operating officer.   The following is a description of the product provided by ScreenMeet:

ScreenMeet is a cloud-based remote support tool designed to integrate with Dynamics 365 Customer Service. By enabling customer service and IT support organizations to address critical technical issues directly from their CRM or ticketing platform, it streamlines the process and provides a fully browser-based support experience.

You can also use ScreenMeet with other CRM products or even on its own without a CRM.

Here is a short video demo of ScreenMeet with Dynamics integration:


ScreenMeet - Cloud-based Remote Support Integrated with Dynamics 365 Customer Support Once integrated with a Dynamics 365 CS organization, the ScreenMeet widget appears on Case pa…

Microsoft PowerApps and Microsoft Flow Licensing for Beginners

NOTE: Since this post was written, Microsoft has updated pricing.  For current pricing, see https://powerapps.microsoft.com/en-us/pricing

Next month marks two years since Microsoft announced the preview of its Flow workflow automation product.  Since then, PowerApps and Microsoft Flow have been gaining in popularity.

We at InfoStrat are receiving more questions from customers on how PowerApps and Flow are licensed by Microsoft.  This is a brief overview with links to authoritative Microsoft resources with all the details.

What are PowerApps and Flow? Microsoft PowerApps is a framework derived from Dynamics 365 (formerly Dynamics CRM) that allow you to build apps either with or without a form interface.  PowerApps works with Microsoft Flow.

Microsoft Flow is is a cloud software tool to build automated workflows that connect to many Microsoft and non-Microsoft systems and services.  For instance, you could write a workflow which would create a record in Dynamics 365 whenever a new file …