Dynamics 365 Rocker's Blog

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

Last week I was working on an existing report. Once I completed my work and want to upload report in CRM, I have encountered with below error. Below are details of log file: Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=7.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: An error occurred while trying to add the report to Microsoft Dynamics CRM. Try adding the report again. If this problem persists, contact your system administrator.Detail: <OrganizationServiceFault xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/xrm/2011/Contracts">   <ErrorCode>-2147188072</ErrorCode>   <ErrorDetails xmlns:d2p1="http://schemas.datacontract.org/2004/07/System.Collections.Generic">     <KeyValuePairOfstringanyType>       <d2p1:key>CallStack</d2p1:key>  ...

  Error:  The date/time format is not valid, or the value is outside the supported range One day, I was getting below error message in a workflow: The reason behind this error was fecth XML. I was using date parameter in condition attribute of fetch XML, Below is image of my code: I have changed date format to “yyyy-MM-dd” and error has been resolved . Cheers, Rocker

If a code passed in UAT then we mostly sure that every thing will work fine in Production.  But It is not always true, Some times we receive error that are not related to code. Same thing happened with me, I have recently received below error in a workflow on production server. The date time format is not Valid in Workflow. Strange thing is that I did not get any such error on dev/test environment. After Spending lot of time, I came to know that “Date and Time “setting was an issue. Main cause was “ Current language for non-Unicode programs ”. It set to United States in my dev/test environment and United Kingdom in production environment. I logged in to CRM production server with same user that is owner of workflow and changed “Current language for non-Unicode programs” to United States and issue has been resolved. To solve this issue, Login with user who is owner of workflow on CRM server and follow below steps: Click on Clock and click on “Change d...