What happened to Microsoft Dynamics CRM and what is Microsoft Dynamics 365?

You may be surprised but you can't find "Microsoft Dynamics CRM" now.

If you are in the IT industry or your business is using CRM then you must be aware of this software.
This particular CRM has three major modules i.e,

  • Sales
  • Service
  • Marketing


Historically, CRM and ERP applications were often independent and monolithic. They required complex deployments.

CRM and ERP were not interrelated and developer effort required to sync data between these applications. It increase the cost as well.

Microsoft tore down the traditional silos of CRM and ERP, bringing them together in a powerful set of applications. This set of applications called Dynamics 365.


Following applications are part of Dynamics 365:

Transactional Applications:

  • Microsoft Dynamics 365 Sales
  • Microsoft Dynamics 365 Marketing
  • Microsoft Dynamics 365 Customer Service
  • Microsoft Dynamics 365 Field Service
  • Microsoft Dynamics 365 Finance
  • Dynamics 365 Supply Chain Management 
  • Dynamics 365 Commerce
  • Microsoft Dynamics 365 Human Resources
  • Microsoft Dynamics 365 Business Central

Analytical Applications:

  • Microsoft Dynamics 365 Sales Insights
  • Microsoft Dynamics 365 Customer Insights
  • Microsoft Dynamics 365 Customer Service Insights
  • Microsoft Dynamics 365 Fraud Protection

Observational Applications:

  • Microsoft Dynamics 365 Remote Assist
  • Microsoft Dynamics 365 Guides

If you want to implement a custom module then you can do it from PowerApps.
PowerApps are part of the Power Platform. You can get information about the power platform in my previous blog.

Why Microsoft did this?

Microsoft wants to provide a 360-degree view to their customer. Now Azure, Dynamics 365 Applications, AI Insights, Mixed Reality, and Power Platform all are interrelated hence there is no need to do any integration between these systems.

Microsoft Dynamics 365 is no code or low code product, Hence there is no need to hire a huge development team.

If a customer wants to use Sales only then they can procure a sales license only and there is no need to get the license for all applications.

If a business wants to implement a custom module then they can go with the PowerApps license only.

 

Stay Connected to get more information about Dynamics 365 and Power Platform.

 

Cheers,

Rocker

 

 

 

Comments

  1. Nanfor Ibérica10 June 2021 at 20:44

    Este blog es realmente útil para ofrecer asuntos actualizados a través de Internet, lo cual es realmente apreciable.
    MB-400: Microsoft Power Apps + Dynamics 365 Developer. Course: MB-400T – nanforiberica

    ReplyDelete

Post a Comment

Popular posts from this blog

Power Automate: Create and attach Dataverse note or activity with an entity record through MS flow

Image
There was a requirement where a note(annotation) will be created once an account is created in Dataverse. I have created a Microsoft flow to achieve this functionality. Below is the screenshot of the flow: It was not a difficult flow but I was getting below error in last step i.e, "Create a note and attach PDF" Resource not found for the segment. The reason for this error was assigning "Account id" in regarding: To resolve the above error, I have set "accounts(Account)" in regarding and it worked. You can also use "/accounts(Account)". Conclusion : Whenever you are creating a #Dataverse note or activity through #MSflow then use "entityname(entityid)" or "/entityname(entityid)" in regarding and don't forget to add suffix "S" in entityname. Cheers, Rocker
Read more

How to send Dataverse email through PowerAutomate

Image
In one of my project requirements, I have to send some recursive email notifications to the account owner. I have chosen Scheduled flow to do this operation, Everything was fine till I created the email. Now, I wonder how to send this email. In traditional Dynamics workflow, we have a "send email" option but there is no such option I can see in flows. What to do now?😓 No worries, After some research, I found "Perform a Bound Action" by which we can send an email. In "Perform a bound action", We have to choose the table as "Email messages", Action name "Send Email" and just mention created email message id in Row Id. Finally, My flow looked like this  That's all, Now the email will be sent from Dataverse. Please subscribe blog for regular updates. Cheers, Rocker
Read more

How to avoid "for each" in Power Automate when there is only one record in Dataverse List rows

Image
There are some situations when we retrieve only a single row. To retrieve an entity record from Dataverse we generally use "List Rows" feature and this always returns an entity collection. Hence we always need to go in "for each" loop. As shown in the below example, I am creating an email on the creation of an account entity record in Dataverse. I have retrieved a queue to set it in "from" activity party of the email. I know that there is only one queue record but I am helpless if I directly select "Dynamic content", It automatically creates a "for each" loop. See in below screenshots: If I go for expression rather than "Dynamic content" then I can avoid "for each" loop, Please refer below screenshot: Below line, I have written in expression: outputs('List_rows_Queue')?['body/value'][0].queueid Here "List_rows_Queue" is the above step, [0] is the first row and "queueid" is a field
Read more