Skip to main content

Understanding Dynamics 365 CRM- Part 1

Introduction:

In this post I plan to walk you through some concepts and functional aspects of CRM module of Dynamics 365. 
We will look into a vast used module of D365 CRM which is Sales in Part 1 of this blog and we shall look into other modules in Part 2

Pre-requisites: 

Microsoft Office 365
An instance of CRM Dynamics 365/ Trial account.

In Case you don't have a trial account, you can create one on https://trials.dynamics.com/,

For details on how to create an account, Visit my post:https://www.exploringdynamics365.tech/2019/10/create-your-own-crm-instance.html

Theory:

CRM as we all know is Customer Relationship Management and is majorly used to maintain data with respect to Sales, Customer Tickets, etc.

We have two major parts to understand for working with CRM, Sales and Customer Service.
In earlier versions of D365 CRM, we had  three modules Marketing, Sales and Customer Service. The New UI however looks like below:


This new UI as we see does not have marketing Module as it is been now combined with Sales.We also have many other modules like field service, project service, etc which we will be exploring later


Talking about the Market Scenario, In every industry we have Marketing departments that organize various Campaigns and  marketing strategies to sell their service /products to the customers.

Through Marketing they get various interested customers, these customers who are basically interested to buy the service/ product are known as leads.

The customer usually is another company, distributor or seller. So once your lead qualifies as your potential customer it becomes an Account and person communicating with regards to buying this service/product becomes the Contact.

Every Account thus has a primary contact( the main person to communicate with) and also may have various related contacts. Similarly, there can be various Accounts represented by a same sales person so a contact may have various Accounts.

After the initial communication the basic details of Accounts, Contact and Lead is updated.
On receiving details about the prospect, an Opportunity is created.

Opportunity in lay man terms will be having all details regarding the Estimated revenue, Start and End dates etc.

Also Sales module has a section for Competitors, which maintains the details of competitors which are trying to grab the same opportunity  we are looking at.


Comments

Post a Comment

Popular posts from this blog

Get Business Process Flow Stage Id using API Query

Developers may need to get the stage ids of BPF stages in order to use in power automate or JS. Here is a blog that will help. API Query-   https:// CRMURL.dynamics.com/ api/data/v9.0/processstages?$select=stagename&$filter=processid/workflowid eq BPFGuid   Eg: 1) Get the GUID of  Business Process Flow whose stage details you need. Replace below Query with Your CRM URL and BPF GUID. https://Test130.crm.dynamics.com/ api/data/v9.0/processstages?$select=stagename&$filter=processid/workflowid eq 9128E4D1-1234-4852-ABD0-A63A6ECA5C5D   Output:    The output will provide the stage name and ID.

Power Automate to Access SharePoint Recycle Bin

Introduction : A ccess Recycle Bin of SharePoint using Power Automate. Steps: Actions: select "Send an HTTP request to SharePoint" Enter the below details: Site Address: Select your site address from the list. Method: GET Uri, Headers: Refer the screenshot below. Pls. Note: Trigger used was When a File is Deleted- SharePoint Connector. Select Action "Parse JSON" In parse JSON, the content is the body of HTTP Response Enter the below Schema: { "type" : "object" , "properties" : { "odata.metadata" : { "type" : "string" }, "value" : { "type" : "array" , "items" : { "type" : "object" , "properties" : { "odata.type" : { "type" : "string" }, "odata.id" : { "type" : "string" }, "odata.editLink" : { "t

Dynamic, Multiple Recipients of D365 Email in Power Automate

When t he activity parties (TO, From, CC) ae static, we can easily send emails. However here is how we can set the activity party dynamically on the Email.    In above screenshot we can see the Activity party attribute is populated for single value and is static to only a single entity record GUID.   Solution: The create a record of Email message is as below, here we are entering the attributes of activity party, by clicking on "Switch to Input entire array" You will get the Array format, the participationtypemask is TO, FROM,CC while the partyid@data.bind is the email address. Now all you need to do is create a dynamic array, You can use append to array variable action to create an array with participationtypemask as per your requirement. Example: get all users whom you need to send email, append the user id to array. pass this array as input to the Activity Parties field in create an email record.