Dynamics 365 Rocker's Blog

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 M...

In simple words, Microsoft Power platform is a place where we can work on the following technologies: PowerApps  Power Automate Power BI  Power Virtual Agents   We can create the following type of components in PowerApps: Model-Driven App : Default app for Microsoft Dataverse or Dynamics 365. We can not connect with other system databases except Microsoft Dataverse. Canvas App : It provides the facility to connect with multiple system databases including Microsoft Dataverse. There are multiple prebuilt connectors available that help us to connect with multiple systems. Power Portal : It is a website for users who do not have an office365 license, Here users can interact with Microsoft Dataverse data. Here we can create flows and do operations in Microsoft Dataverse as well as in other systems. There are multiple prebuilt connectors available that help us to connect a flow with multiple databases. For eg, A task record should be created in Dynamics 365 if we get a tweet on...

Last month Microsoft changed the name of Common Data Service to  Microsoft Dataverse or Dataverse. There are the following changes in terms that we used to call in CDS: CDS Term Dataverse Term Entity Table Attribute/Field Column Optionset /Multiple Optionset Choice Two Option Yes/No Record Row But there is no change in API or web service, CreateEntityRequest is still called as CreateEntityRequest. Have a look at Power App to see the changes: But these changes are not reflected in Dynamics365 Solution. We can find the old term there i.e. "entity and option set" but the same solution in the power app reflects the new term i.e. Table, Choice etc. Solution in Dynamics 365  Solution in PowerApp CDS connector in Power App still has the name "Common Data Service", It may or may not change in the future. Solutions in Dynamics 365 may or ma...

Few months before,I got a task to automate solution deployment process through Powerapps Build tools. Before doing this , I had no experience in AzureDevops. Hence I am sharing my experience through this blog that may be helpful to non Devops guys who are working in Dynamics365. Step1: Create a folder and Solution files in Master branch. Step 2: Click on Release then Pipelines and Click on "Create Pipeline" Then click on "Use classic editor" as highlighted in below image. Select "Azure Repos Git" and select correct "Team Project", "Repository" and "Branch as Master" then click on continue. Click on "Empty Job" as mentioned in below image. As per below image , You can add a task by clicking on highlighted "+" button and search for PowerApps tools  and get it or install it. Once you install it then click on "+" button  as highlighted in...

One day, We were getting below error while accessing Advanced Settings of Dynamics365 CE. Even System administrator was also getting same error. This issue was related to Sitemap. Actually our Sitemap has been corrupted, To resolve this issue, take backup of sitemap from other CRM environment and import it on environment where this error is coming. I have posted this on Community and get resolution of it. To know more about it please follow below post: https://community.dynamics.com/crm/f/microsoft-dynamics-crm-forum/381761/if-you-are-the-administrator-you-can-go-to-the-solutions-page-and-import-a-different-solution Cheers, Rocker

If you are a CRM developer and want to write Client Script in Dynamics 365 then you are at right place. There are huge changes in Client API in Dynamics 365 for Customer Engagement. From CRM 2011 we are familiar with   XRM.Page but it is deprecated in Dynamics 365 for Customer engagement and it has been replaced with ExecutionContext. getFormContext . What is Execution Context : The execution context defines the event context in which your code executes. The execution context is passed when an event occurs on a form or grid, which you can use it in your event handler to perform various tasks such as determine  formContext  or  gridContext , or manage the save event. Execution context was already in previous version of CRM but we can easily access other client API by XRM.Page hence we did not use it always. You will get more details at below link: https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/clientapi/clientapi-e...

One day one of my team member faced below error while activating a workflow: Reason of this error is owner of workflow, Actually that particular user is disabled in CRM.    To resolve this issue assign that particular workflow to your self or system admin then activate it. Cheers, Rocker