FakeXrmEasy is an invaluable tool for development of Dynamics CRM/365/Dataverse software and using it will make your life as a developer much easier and will undoubtedly help you write more robust, maintainable code. FakeXrmEasy implements an in-memory version of the XRM database and provides mocked version of most of the main methods provided by the IOrganisation service. You may, however, occasionally come across a method which has not been implemented in the library. When you test code which calls one of these methods, your test will fail with a message like this: The organization request type 'Microsoft.Crm.Sdk.Messages.NameOfTheUnimplementedRequest' is not yet supported... but we DO love pull requests so please feel free to submit one! :). This functionality is not available yet. Please consider contributing to the following Git project https://github.com/jordimontana82/fake-xrm-easy by cloning the repository and issuing a pull request."

In this article I will demonstrate how you can use a LINQPad script to very quickly update Dynamics Solution Numbers in a consistent way across all of your solutions.

In the first part of this multi-part series of articles about creating connections in LINQPad to Dynamics 365 online, I went through the basic steps needed to create an OrganizationService connection in a LINQPad script.

Handling MFA connections to Dynamics 365
In the first part of this multi-part series of articles about creating connections in LINQPad to Dynamics 365 online, I went through the basic steps needed to create an OrganizationService connection in your LINQPad script.

LINQPad is an invaluable tool for .Net developers in general and as a Dynamics developer being able to test and execute code using the Dynamics365 API using LINQPad can be a real timesaver. In this multi-part series of articles, I will show you how to configure LINQPad so that creating connections to Dynamics365 can be done quickly and easily. Using the MyExtensions file, you’ll be able to create a shared method for every member of your team to be able to connect to any of your Dynamics environments by just typing a single line of code.

If you have used an attribute in a saved view in Dynamics, and the attribute is removed from the entity, you will get the following error when you try and access the view:

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

On creating a new plugins project for our Dynamics 2015 organisation with the latest version of the Dynamics 365 Developer Toolkit we were experiencing all sorts of errors, either on deployment or on execution.

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.