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:

• Test the correct implementation of security roles.
• Check which records can be seen by which users if sharing is being used.
• Search for charts or views belonging to different users.
• Test the behaviour of plugins when executed by users wth different security roles.
  

LINQPad is an invaluable tool for any .Net developer, and it will greatly enhance your ability to write and support applications using Dynamics CRM. There are two ways with which to connect to an instance of Microsoft Dynamics CRM using LINQPad. This two-part article will describe these two different methods and examine the reasons why you might choose one over the other.