“
CRM Market Share by Vendors
18% – SalesForce
12% – SAP
9% – Oracle
6% – Microsoft
4% – IBM
51% – Rest of CRM providers
”

Dynamics CRM holds a wealth of information about customers and the sales pipeline.

Customer Relationship Management platform offered by Microsoft is 360 degree flexible that allows system customizers to enhance its capabilities to map to any kind of business and scale to any size.

Through this blog discussion, we will keep our focus limited to creating, customizing and extending entities, a vital key feature of Dynamics CRM.

In this article, we shall see throughout working with entities

In Microsoft Dynamics CRM, every customization work is achieved through the solution, which is essentially a container of all the configurations and customizations.

This kind of packaging allows customizers

Further, there exists two kinds of customizations / solutions:

The guidance provided by Microsoft when working with any of two types of solutions states that a solution should be used in an unmanaged state while it is rolling out in development and test environments. And once solution is completed, it should be exported as a managed solution, at the time when it is in the ready state to be deployed to a production environment.

Managing solutions is an aspect that should not be taken lightly, as down the road, a properly designed solution packaging model can help a lot, while incorrect one can limit possibilities and create difficulties.
To leverage customization options, we will extend the system to fit new business requirements by creating an entity.

Broadly, any Dynamics CRM application is structured into four main categories or fragments as follows:

Entities are considered core application elements.

At its core, Entities are objects/containers used to

business data.

Through the use of entities, the platform allows us to

Each entity is comprised of a various number of attributes.

These attributes are, in fact, data items of a particular type stored in the database.

Each one of these attributes can be displayed on an entity form as a field.

For example, an account will have

and many others.

To give an analogous example, we can think of each entity as a table, or an excel spreadsheet where each column is an attribute.

Within Dynamics CRM, entities are classified into three major categories.

Business and Custom entities can be configured as

Any entity that is customizable can be modified by

associated with it.

*Shared entities are NOT 4th special type of entity, rather they are entities used across multiple modules.

“Microsoft Dynamics CRM wins 2016 CUSTOMER Magazine CRM Excellence Award.”

Having adequate background on Dynamics 365 application, we shall now delve deeper and take a look at how to create, customize and use entities, including

We will exercise Entity creation work with the elements of any of three modules namely

modules.

We will grasp the concept of ‘Create Entity’ by example of a medical insurance provider.

In an insurance company, claims team needs to detail day-to-day process after discussions with clients. Then they forward series of reports to senior management, where claim’s bill is approved/rejected based on evaluation and terms.We need to plan out this section/add user interfaces and functionality for the same out of the solution.

Considerate the insurance industry domain process, the claims processing team needs to know

Senior management is interested to know

With any Dynamics 365 deployment, there are more than one ways to accomplish the same set of objectives.

Here, we will walk through creating a claims entity and add the relevant fields to same for accurate processing.

However, another valid approach available is to repurpose the out-of-the-box Claims entity and customize it to adjust in our business context.

Also, there are plenty of things to consider when planning process structure , such as

As this is an illustration, we will keep it to simple implementation.

As depicted in below screenshot, from the Components area within the solution, click New Entity.

Enter appropriate information for all the fields like that for

and save it.

Since the claims processing team has ownership of a Claim, the Ownership needs to be set to User or Team.

This is something you cannot change after creating the entity. The other option is Organization, which means no user has ownership of the record.

Besides the basic information for the entity, you need to to fill out seven sections when creating an Entity:

Here, we will keep it simple. That is, our claims entity is owned by a user or team, available within Service, with Activities and Notes, that is audited.

Once the entity is created, there are certainly two ways to add more fields to it. First, via Fields within the Claim entity

The second (and probably more intuitive) way is through the Field Explorer on the form you want to operate.

Revisiting the requirements, the claims processing team needs to know

Notice that ownership field is autonomously created when we selected the user or team while creating the Claims entity.

To meet requirements, we can add ‘Priority Level’ field and it should be packed with options of High, Normal, and Low.

If you are starting off a Dynamics project and are planning to enhance the CRM system, make sure to consult with subject matter experts to explore day-to-day process in detail.

You need to analyze the current data model elaborately – this ought to help you elect perfect data types for all the fields – neither oversized nor under estimated.

Variance Infotech helps clients with any part of the Dynamics 365 project. Whether you are just kicking off a new project, or struggling in the middle of the process to make it more user friendly, developers at Variance Infotech are fully capable to elucidate and resolve any complex problem.

Do You Need more information ?

For any further information / query regarding Technology, please email us at info@varianceinfotech.com OR call us on +1 630 861 8263, Alternately you can request for information by filling up Contact Us