Dynamics CRM 2013 includes a great new feature called access teams, which makes ad-hoc sharing of records much easier than in previous versions. The basic idea is that an administrator can create one or more team templates for an entity that function sort of like security roles, but for a specific record. »
In my last post, I talked about what Dynamics CRM 2013 actions are and how I think they’re of limited utility in enterprise deployments. I did suggest two scenarios in which I think actions could be useful, and I’m sure other folks may have come up with some ideas of their own. »
I finally set up a personal Dynamics CRM 2013 sandbox a couple of weeks ago so I could start trying out some of its new features. Although I had been waiting for most of the Fall to get a look at real-time workflows, I was also intrigued by the new action process. »
One of the main points of all my unit testing posts is that unit tests should be written so that you can test your code without needing to rely on external resources, and, we’ve been able to use Moq as a stand-in for Dynamics CRM’s related services without too much trouble. »
This is the final post in my series on unit testing custom Microsoft Dynamics CRM code in which I’ve been showing how you can unit test custom C# code that interacts with Microsoft Dynamics CRM using Visual Studio’s unit testing tools and Moq. We’ve looked at several different scenarios thus far, but none of them included the method under test throwing an exception. »