I love Dynamics CRM dialogs. In fact, I think they are one of the best features of CRM 2011. What I don’t like about dialogs is how the user has to run them when working with a entity record. On a “classic” mode form, the user has to go to the ribbon, click start dialog and then find the dialog in a list. »
Back in January, after I published my How to unit test C# Dynamics CRM interface code - part III post on how to use NUnit and Moq to test Dynamics CRM interfacing code, I uploaded my project files to the MSDN code gallery. Earlier this week I revisited my original solution while preparing a demo for some of my colleagues. »
In this post I will show how to document a Dynamics CRM 2011 custom workflow activity assembly and use Doxygen to generate a compiled HTML (CHM) help file. (Doxygen can actually generate documentation in a variety of different formats, but I’m partial to CHM files because they’re entirely self-contained.) For this example, I have a project that consists of these three C# files: »
With the proliferation of RESTful APIs, JSON is frequently used as a message format for interoperability. My MSDN “Posting/processing JSON in a CRM 2011 custom workflow activity” code sample shows how to POST JSON messages to a REST endpoint and process the response in a Dynamics CRM custom workflow activity. »
In this post I will show how to send SMS messages and make automated phone calls from Dynamics CRM using Tropo, a cloud voice and SMS messaging API. Tropo is not the only player in this space, but I think it has the best set of features, and it’s completely free to use in development. »