Thursday 6 December 2018

Build Numbers for Dynamics CRM

I was tasked to get all the build numbers for every version of Microsoft Dynamics CRM version released which made me curious as to why I had not documented it.

My research brought me to this page. A comprehensive list of all build numbers of Microsoft Dynamics CRM.

Click Build Numbers for Microsoft Dynamics CRM to get it.


Friday 2 November 2018

Plugin Registration Tool Crashes

My Plugin registration was working perfectly not until it decided not to when I needed it most.

This happened to Plugin Reg. Tool V9. Basically, I just cleared the files in the folder

C:\<your username>\AppData\Roaming\Microsoft\PluginRegistration

Below is my source of the solution.

Quick Fix to Plugin Registration Tool crashing by Yawer.

Monday 11 June 2018

Quick Fix: Visual Studio 2017 displaying NAV Report Layout as XML

My colleague tried to open a report from NAV 2018 on VS2017 and he had issues because the report only showed the XML view.
He was not expecting this and could not make sense out of it.
We searched for answers and saw

A great article from Kushal Pillay
Quick fix: VS 2017 displaying NAV Report Layout as XML

and also Shashangka Shekhar
Enable RDLC Reporting in Visual Studio 2017

The steps were followed and the issue was resolved


Monday 8 January 2018

Authentication Issue with Web App for Dynamics 356 v9

I was unable to connect to Dynamics 356 Customer Engagement through a web application.
There were different errors I got based on the method used to connect to CRM

For Xrm.Tooling.Connector
Error message: OrganizationServiceProxy is null
LastCrmError: "Unable to Login to CRM OrganizationServiceProxy is null"

For Web service OrganizationService
Error: Metadata contains a reference that cannot be resolved: ‘https://***.api.crm4.dynamics.com/XRMServices/2011/Organization.svc?wsdl&sdkversion=9

During my search for a resolve, which took me days, I stumbled upon this blog
Abhinav Ranjan

Following this link by Microsoft New features of Dynamics 365 Customer Engagement. It explained the possible ways to resolve it.

Adding this piece of code before authentication resolves the issue

ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12