“I’d like my FetchXML with double quotes, please”, said no Dynamics developer, ever.
The ‘additive’ nature of CRM deployments means that it can be easier to add components to an instance of CRM than it is to remove them.
When writing Unit tests one can focus on two different aspects of the code under test. We can call these two types of test ‘State-based’ and ‘Interaction-based’. The first of these concentrates on the end result achieved by the code under test – ie, what was the result of the code being run, whereas the second focuses on how that result was achieved.
Our automated deployment of a CRM Solution file started failing with this error recently:
"importjob With Id = feb7b87f-1ff9-4914-ba14-0116ca959584 Does Not Exist"
It was quite a journey to find out what was causing the error.
When trying to compile a FetchXML-based report in Visual Studio 2015 which had been developed in an earlier version of Visual Studio, we were getting the following error:
While you can’t ordinarily log in as another user through the Dynamics CRM/365 front end, as a System Administrator it is possible to impersonate another user when making calls to the CRM API.
This is very useful if you want to be able to do the following: