Common Standard Entity and its Uses

In this section, we shall now discuss some of the common standard entity and how to use it. Primarily, the account and contact entities in Microsoft Dataverse are important to identify and manage customers, selling products and services, for offering superior service to the customers. On the other hand, a customer address entity is primarily used to store address and shipping information for a customer.

Account Entity

To begin with, the account entity is one of the entities in Dataverse to which most other entities are associated or parented. Moreover, in Dataverse, an account shows a company with which the business unit has a relationship. Moreover, the information included in an account is all relevant contact information, company information, category, relationship type, and address information. Some information applied includes –

• Firstly, an account that can be a parent to almost any other entity.
• Secondly, an account that can be a standalone entity.
• Next, an account that can have only one account as its parent.
• Lastly, accounts can have multiple child accounts and child contacts.

Certainly, account management is considered one of the most crucial concepts of business-to-business customer relationship management (Dynamics 365). Since every organization wants to see all the activities they have with another company.

Contact Entity

A contact related to a person, an individual, with whom a business unit has a relationship, In Dataverse including a customer, a supplier, or a colleague. Further, the contact entity is one of the entities that most other entities are linked to such that contact can be a stand-alone entity. The contact entity includes professional, personal, and family information, and multiple addresses. It stores all information about a person including email address, street address, telephone numbers, and other related information, such as the birthday or anniversary date. Depending on the type of customers a business unit has, it needs either only contacts, or contacts and accounts, to offer a full view of its customers. The basic operations that you can perform on contact include Create, Read, Update, and Delete.

However, both accounts and contacts are part of managing customers are related to one another in the given manner –

• Firstly, contact can be a parent to every other entity except accounts and contacts.
• Secondly, contact can have only one account as its parent.
• Lastly, contact can be marked as the primary contact person for an account by using the Update method.

CustomerAddress Entity

CistomAddress entity contains address and shipping information. Also, it is used to store additional addresses for an account or contact. The Customer Address table is updated at the platform level when a change is made to the Account or Contact entities. As a result, no separate SDK call will be made to update or create the Customer Address entity. Therefore any code that is triggering on address updates or creates should be pointing to the Contact or Account entities.

Learn more about Common Standard Entity