<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>programming on Alexander Development</title><link>https://alexanderdevelopment.net/tag/programming/</link><description>Recent content in programming on Alexander Development</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 15 Jan 2018 14:58:00 +0000</lastBuildDate><atom:link href="https://alexanderdevelopment.net/tag/programming/index.xml" rel="self" type="application/rss+xml"/><item><title>Accessing an on-premises Dynamics 365 organization from Python</title><link>https://alexanderdevelopment.net/post/2018/01/15/connecting-to-an-on-premise-dynamics-365-org-from-python/</link><pubDate>Mon, 15 Jan 2018 14:58:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2018/01/15/connecting-to-an-on-premise-dynamics-365-org-from-python/</guid><description>I&amp;rsquo;ve previously showed how to access online and IFD instances of Dynamics 365 Customer Engagement from Python code. Because that sample code authenticated to the Web API using OAuth, it won&amp;rsquo;t work with on-premises instances. Recently I&amp;rsquo;ve been doing some work with Python and an on-premises Dynamics 365 organization, so I thought I&amp;rsquo;d share a sample that shows how to authenticate to the Web API using NTLM.</description></item><item><title>Dynamics 365 and Python integration using the Web API - part 2</title><link>https://alexanderdevelopment.net/post/2017/02/19/dynamics-365-and-python-integration-using-the-web-api-part-2/</link><pubDate>Sun, 19 Feb 2017 21:15:02 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2017/02/19/dynamics-365-and-python-integration-using-the-web-api-part-2/</guid><description>Last week I wrote a post that showed how to update Dynamics 365 data from a Node.js application using the Web API. Today I will share equivalent Python code. This code builds on my Dynamics 365 and Python integration using the Web API post from last year, so if you haven&amp;rsquo;t read that yet, please take a look before you proceed.</description></item><item><title>Dynamics 365 and Node.js integration using the Web API - part 2</title><link>https://alexanderdevelopment.net/post/2017/02/16/dynamics-365-and-node-js-integration-using-the-web-api-part-2/</link><pubDate>Thu, 16 Feb 2017 17:05:52 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2017/02/16/dynamics-365-and-node-js-integration-using-the-web-api-part-2/</guid><description>Last year I wrote a post that showed how to retrieve data from a Dynamics 365 Online organization in a Node.js application using the Web API. Today I will share sample code that shows how to update data from a Node.js application using the Web API.
####Updating a single property To update a single property on a record in Dynamics 365, you can make a PUT request to the Web API.</description></item><item><title>Dynamics 365 and Python integration using the Web API</title><link>https://alexanderdevelopment.net/post/2016/11/27/dynamics-365-and-python-integration-using-the-web-api/</link><pubDate>Sun, 27 Nov 2016 15:12:31 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2016/11/27/dynamics-365-and-python-integration-using-the-web-api/</guid><description>A few days back I wrote a post that showed an easy way to set up Dynamics 365 and Node.js integration using the Web API. Here is Python code that demonstrates equivalent functionality to query contacts and display their information:
import requests import json #set these values to retrieve the oauth token crmorg = &amp;#39;https://CRMORG.</description></item><item><title>Dynamics 365 and Node.js integration using the Web API</title><link>https://alexanderdevelopment.net/post/2016/11/23/dynamics-365-and-node-js-integration-using-the-web-api/</link><pubDate>Wed, 23 Nov 2016 16:17:09 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2016/11/23/dynamics-365-and-node-js-integration-using-the-web-api/</guid><description>I wrote a blog post in early 2015 that showed how to access the Dynamics CRM organization data service from a Node.js application. Today I will show an easy way to retrieve data from a Dynamics 365 Online organization in a Node.js application using the Web API.
Unlike the CRM organization service, the Dynamics 365 Web API does not allow you to authenticate directly with a user name and password.</description></item><item><title>Updated solution for scheduling recurring Dynamics CRM workflows</title><link>https://alexanderdevelopment.net/post/2016/09/19/updated-solution-for-scheduling-recurring-dynamics-crm-workflows/</link><pubDate>Mon, 19 Sep 2016 21:07:07 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2016/09/19/updated-solution-for-scheduling-recurring-dynamics-crm-workflows/</guid><description>About three years ago I released an open source Dynamics CRM solution for scheduling and executing recurring workflows. My solution would execute a FetchXML query to return a set of records and then start a workflow for each of those records without requiring any external processes or tools. This is a generalized approach to solving a class of problems that includes the following scenarios:</description></item><item><title>Console application for moving Dynamics CRM access team templates</title><link>https://alexanderdevelopment.net/post/2014/12/13/console-application-for-moving-dynamics-crm-access-team-templates/</link><pubDate>Sat, 13 Dec 2014 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2014/12/13/console-application-for-moving-dynamics-crm-access-team-templates/</guid><description>When Dynamics CRM 2013 was released, I thought access teams were the new killer feature in that version, and I even developed custom workflow activity code to make managing access team membership easier by using connection records. I have thus far not had an opportunity to use access teams in a real project, so I was disappointed to read this blog post by Ben Hosking (AKA &amp;ldquo;The Hosk&amp;rdquo;) about how Microsoft doesn&amp;rsquo;t provide any out-of-the-box capabilities for moving access team templates between Dynamics CRM organizations.</description></item><item><title>Unit testing custom Microsoft Dynamics CRM code – Part 7 (web requests)</title><link>https://alexanderdevelopment.net/post/2013/10/24/unit-testing-custom-microsoft-dynamics-crm-code-part-7-web-requests/</link><pubDate>Thu, 24 Oct 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/10/24/unit-testing-custom-microsoft-dynamics-crm-code-part-7-web-requests/</guid><description>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&amp;rsquo;ve been able to use Moq as a stand-in for Dynamics CRM’s related services without too much trouble.</description></item><item><title>Unit testing custom Microsoft Dynamics CRM code – Part 8 (exception raising)</title><link>https://alexanderdevelopment.net/post/2013/10/24/unit-testing-custom-microsoft-dynamics-crm-code-part-8-exception-raising/</link><pubDate>Thu, 24 Oct 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/10/24/unit-testing-custom-microsoft-dynamics-crm-code-part-8-exception-raising/</guid><description>This is the final post in my series on unit testing custom Microsoft Dynamics CRM code in which I&amp;rsquo;ve been showing how you can unit test custom C# code that interacts with Microsoft Dynamics CRM using Visual Studio&amp;rsquo;s unit testing tools and Moq. We&amp;rsquo;ve looked at several different scenarios thus far, but none of them included the method under test throwing an exception.</description></item><item><title>Unit testing custom Microsoft Dynamics CRM code – Part 6 (plug-ins)</title><link>https://alexanderdevelopment.net/post/2013/10/21/unit-testing-custom-microsoft-dynamics-crm-code-part-6-plug-ins/</link><pubDate>Mon, 21 Oct 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/10/21/unit-testing-custom-microsoft-dynamics-crm-code-part-6-plug-ins/</guid><description>In my last post, I showed how to unit test a Microsoft Dynamics CRM custom workflow activity using Visual Studio and Moq. In this post I will show you how to unit test a Dynamics CRM plug-in. For this example we&amp;rsquo;ll be using the sample FollowupPlugin class in the CRM 2011 SDK, but the principles I will demonstrate are applicable to any plug-in.</description></item><item><title>Unit testing custom Microsoft Dynamics CRM code – Part 5 (custom workflow activities)</title><link>https://alexanderdevelopment.net/post/2013/10/17/unit-testing-custom-microsoft-dynamics-crm-code-part-5/</link><pubDate>Thu, 17 Oct 2013 18:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/10/17/unit-testing-custom-microsoft-dynamics-crm-code-part-5/</guid><description>In the last three posts of this series, I showed how to unit test Microsoft Dynamics CRM C# interfaces code with mock objects using Visual Studio 2012 and Moq. In this post, I will show how to unit test custom workflow activities that are executed by Dynamics CRM processes. I will be using the regular expression validation custom workflow activity I showed in my &amp;ldquo;Using regular expressions in Dynamics CRM 2011 processes&amp;rdquo; post.</description></item><item><title>Unit testing custom Microsoft Dynamics CRM code – Part 4 (using a wrapper class)</title><link>https://alexanderdevelopment.net/post/2013/10/17/unit-testing-custom-microsoft-dynamics-crm-code-part-4/</link><pubDate>Thu, 17 Oct 2013 17:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/10/17/unit-testing-custom-microsoft-dynamics-crm-code-part-4/</guid><description>In parts two and three of this series, I gave an introduction to unit testing Dynamics CRM C# interfaces code with mock objects using Visual Studio 2012 and Moq, and I showed code samples for a couple of different scenarios. In this post I will show how to work with CRM metadata (optionset values, statuscode values, etc.</description></item><item><title>Unit testing custom Microsoft Dynamics CRM code – Part 3 (intermediate interface example)</title><link>https://alexanderdevelopment.net/post/2013/10/10/unit-testing-custom-microsoft-dynamics-crm-code-part-3/</link><pubDate>Thu, 10 Oct 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/10/10/unit-testing-custom-microsoft-dynamics-crm-code-part-3/</guid><description>In my last post I gave an introduction to unit testing Dynamics CRM C# interfaces code with mock objects using Visual Studio 2012 and Moq. The sample code in that post was extremely simple, so I wanted to follow up with a more complex example that shows how to test multiple calls to the CRM web service instead of just a single one.</description></item><item><title>Unit testing custom Microsoft Dynamics CRM code – Part 2 (simple interface example)</title><link>https://alexanderdevelopment.net/post/2013/10/09/unit-testing-custom-microsoft-dynamics-crm-code-part-2/</link><pubDate>Wed, 09 Oct 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/10/09/unit-testing-custom-microsoft-dynamics-crm-code-part-2/</guid><description>In my last post I explained why you should unit test your Dynamics CRM-facing code using frameworks to handle both testing automation and mock objects. In this post, I&amp;rsquo;m going to provide an overview of how to get started.
As I mentioned last time, we&amp;rsquo;ll be using the unit testing tools included in Visual Studio 2012 for the unit testing automation and Moq for the object mocking.</description></item><item><title>Unit testing custom Microsoft Dynamics CRM code – Part 1 (series introduction)</title><link>https://alexanderdevelopment.net/post/2013/10/02/unit-testing-custom-microsoft-dynamics-crm-code-part-1/</link><pubDate>Wed, 02 Oct 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/10/02/unit-testing-custom-microsoft-dynamics-crm-code-part-1/</guid><description>When writing custom code that interacts with Microsoft Dynamics CRM, it is important to:
Unit test your code Use an automated unit testing framework to automate your unit tests Write unit tests that do not depend on external resources such as a Microsoft Dynamics CRM application server or SQL Server Over the course of my next several posts, I&amp;rsquo;ll be showing you some best practices for unit testing Dynamics CRM-facing code using Visual Studio unit testing tools and the Moq object mocking library.</description></item><item><title>A Better Dynamics CRM E-mail Editor With TinyMCE (updated for IE8 and 9)</title><link>https://alexanderdevelopment.net/post/2013/08/15/a-better-dynamics-crm-e-mail-editor-with-tinymce-updated-for-ie8-and-9/</link><pubDate>Thu, 15 Aug 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/08/15/a-better-dynamics-crm-e-mail-editor-with-tinymce-updated-for-ie8-and-9/</guid><description>When I developed the JavaScript for my A Better Dynamics CRM E-mail Editor With TinyMCE post back in June, I tested it in both Chrome and IE10. Since then I have gotten a few reports of it not working in IE8 or IE9. Initially, I thought there might be a problem with the way the earlier versions of IE were handling the protocol-relative URLs to the TinyMCE CDN script, but it turned out that the script just wasn&amp;rsquo;t loading properly when the editor popup was initially launched.</description></item><item><title>Diesel Xrm Service Wrapper Now on GitHub</title><link>https://alexanderdevelopment.net/post/2013/08/05/diesel-xrm-service-wrapper-now-on-github/</link><pubDate>Mon, 05 Aug 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/08/05/diesel-xrm-service-wrapper-now-on-github/</guid><description>Last week I wrote a post called &amp;ldquo;Introducing the Diesel Xrm Service Wrapper,&amp;rdquo; in which I presented a generic WCF wrapper for the Dynamics CRM Organization Service. Almost immediately I had several ideas about updates I wanted to make, so I&amp;rsquo;ve decided to host the project on GitHub. The project GitHub page is here, and you can find the code repository here.</description></item><item><title>Introducing the Diesel Xrm Service Wrapper</title><link>https://alexanderdevelopment.net/post/2013/07/31/introducing-the-diesel-xrm-service-wrapper/</link><pubDate>Wed, 31 Jul 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/07/31/introducing-the-diesel-xrm-service-wrapper/</guid><description>In this post, I will present a generic Windows Communication Foundation (WCF) wrapper for the Dynamics CRM Organization Service that lets you turn any FetchXML query into a web service interface without needing to write any code at all. I call my solution the Diesel Xrm Service Wrapper after Diesel, my Great Dane.</description></item><item><title>A Data Snapshot Framework for Dynamics CRM</title><link>https://alexanderdevelopment.net/post/2013/07/24/data-snapshot-framework-for-dynamics-crm/</link><pubDate>Wed, 24 Jul 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/07/24/data-snapshot-framework-for-dynamics-crm/</guid><description>Although Dynamics CRM offers several different ways to report on data stored in the system, there is no out-of-the-box mechanism for reporting on how data changes over time. That is to say, while you can easily report on how many active accounts are owned by a particular sales rep today, you can&amp;rsquo;t report on how the number of active account compares to last week, last month or even just yesterday.</description></item><item><title>A Better Dynamics CRM E-mail Editor With Markdown</title><link>https://alexanderdevelopment.net/post/2013/07/09/a-better-dynamics-crm-e-mail-editor-with-markdown/</link><pubDate>Tue, 09 Jul 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/07/09/a-better-dynamics-crm-e-mail-editor-with-markdown/</guid><description>Last month I wrote a post called A Better Dynamics CRM E-mail Editor With TinyMCE in which I showed how to create a better Dynamics CRM e-mail editing interface using TinyMCE. Since then I have done some work with Markdown, and I decided it would be an interesting exercise to make a Markdown-enabled e-mail editor.</description></item><item><title>A Better Dynamics CRM E-mail Editor With TinyMCE</title><link>https://alexanderdevelopment.net/post/2013/06/26/a-better-dynamics-crm-e-mail-editor-with-tinymce/</link><pubDate>Wed, 26 Jun 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/06/26/a-better-dynamics-crm-e-mail-editor-with-tinymce/</guid><description>I think most people would agree the e-mail editing functionality in the Dynamics CRM web UI leaves a lot to be desired. One of the most embarrassing moments I experienced on a recent project was when I had to explain to the client the convoluted process that would need to be used to add a corporate logo to outbound e-mails.</description></item><item><title>Creating a dynamic dialog launcher menu for Dynamics CRM (FetchXML style)</title><link>https://alexanderdevelopment.net/post/2013/06/03/creating-a-dynamic-dialog-launcher-menu-for-dynamics-crm-fetchxml-style-2/</link><pubDate>Mon, 03 Jun 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/06/03/creating-a-dynamic-dialog-launcher-menu-for-dynamics-crm-fetchxml-style-2/</guid><description>Last month I wrote a post about how to create a web resource dialog &amp;ldquo;launcher&amp;rdquo; that you can embed in a CRM form (both classic and updated modes) with JavaScript and an OData query. In today&amp;rsquo;s post, I will show how to do the same thing using a FetchXML query. There are four changes you need to make to the web resource from the previous post.</description></item><item><title>Scheduling recurring Dynamics CRM workflows with FetchXML</title><link>https://alexanderdevelopment.net/post/2013/05/19/scheduling-recurring-dynamics-crm-workflows-with-fetchxml/</link><pubDate>Sun, 19 May 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/05/19/scheduling-recurring-dynamics-crm-workflows-with-fetchxml/</guid><description>In today&amp;rsquo;s post I will show how to set up a recurring process in Dynamics CRM that executes a FetchXML query to return a set of records and then starts a workflow for each of those records without requiring any external processes or tools. This is a generalized approach to solving a class of problems that includes the following scenarios:</description></item><item><title>Creating a dynamic dialog launcher menu for Dynamics CRM</title><link>https://alexanderdevelopment.net/post/2013/05/17/creating-a-dynamic-dialog-launcher-menu-for-dynamics-crm/</link><pubDate>Fri, 17 May 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/05/17/creating-a-dynamic-dialog-launcher-menu-for-dynamics-crm/</guid><description>I love Dynamics CRM dialogs. In fact, I think they are one of the best features of CRM 2011. What I don&amp;rsquo;t like about dialogs is how the user has to run them when working with a entity record. On a &amp;ldquo;classic&amp;rdquo; mode form, the user has to go to the ribbon, click start dialog and then find the dialog in a list.</description></item><item><title>Updated "Unit testing Dynamics CRM C# interfaces code using NUnit and Moq" code sample</title><link>https://alexanderdevelopment.net/post/2013/05/01/updated-unit-testing-dynamics-crm-c-interfaces-code-using-nunit-and-moq-code-sample/</link><pubDate>Wed, 01 May 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/05/01/updated-unit-testing-dynamics-crm-c-interfaces-code-using-nunit-and-moq-code-sample/</guid><description>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.</description></item><item><title>Documenting a Dynamics CRM custom workflow activity with Doxygen</title><link>https://alexanderdevelopment.net/post/2013/04/30/documenting-dynamics-crm-interfacing-code-with-doxygen/</link><pubDate>Tue, 30 Apr 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/04/30/documenting-dynamics-crm-interfacing-code-with-doxygen/</guid><description>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&amp;rsquo;m partial to CHM files because they&amp;rsquo;re entirely self-contained.) For this example, I have a project that consists of these three C# files:</description></item><item><title>Posting/processing JSON in a Dynamics CRM 2011 custom workflow activity</title><link>https://alexanderdevelopment.net/post/2013/04/22/postingprocessing-json-in-a-crm-2011-custom-workflow-activity/</link><pubDate>Mon, 22 Apr 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/04/22/postingprocessing-json-in-a-crm-2011-custom-workflow-activity/</guid><description>With the proliferation of RESTful APIs, JSON is frequently used as a message format for interoperability. My MSDN &amp;ldquo;Posting/processing JSON in a CRM 2011 custom workflow activity&amp;rdquo; code sample shows how to POST JSON messages to a REST endpoint and process the response in a Dynamics CRM custom workflow activity.</description></item><item><title>Sending SMS messages and making robocalls from Dynamics CRM</title><link>https://alexanderdevelopment.net/post/2013/04/21/sending-sms-messages-and-making-robocalls-from-dynamics-crm/</link><pubDate>Sun, 21 Apr 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/04/21/sending-sms-messages-and-making-robocalls-from-dynamics-crm/</guid><description>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&amp;rsquo;s completely free to use in development.</description></item><item><title>Displaying Dynamics CRM FetchXML results in ASPX with XSLT</title><link>https://alexanderdevelopment.net/post/2013/02/27/displaying-dynamics-crm-fetchxml-results-xslt/</link><pubDate>Wed, 27 Feb 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/02/27/displaying-dynamics-crm-fetchxml-results-xslt/</guid><description>Last week I wrote a post that showed how to retrive the raw SOAP response from a Dynamics CRM query in C#, but I didn&amp;rsquo;t show how to do anything useful with it. In today&amp;rsquo;s post I will show a practical example of how to execute a FetchXML request against a Dynamics CRM instance, capture the raw SOAP response and transform it with XSLT for display in an ASPX page.</description></item><item><title>Accessing raw SOAP requests/responses from Dynamics CRM web services in C#</title><link>https://alexanderdevelopment.net/post/2013/02/21/accessing-raw-soap-requests-responses-from-dynamics-crm-web-services-in-c/</link><pubDate>Thu, 21 Feb 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/02/21/accessing-raw-soap-requests-responses-from-dynamics-crm-web-services-in-c/</guid><description>One of the things I have always found frustrating about WCF is that it effectively hides the actual SOAP message XML requests and responses in web service calls. From a Dynamics CRM perspective, I can think of at least three good reasons it would be nice to be able to access the raw XML generated and consumed by clients built with the SDK:</description></item><item><title>Misadventures with CRM 2011 web services and ADFS</title><link>https://alexanderdevelopment.net/post/2013/02/17/misadventures-with-crm-2011-web-services-and-adfs/</link><pubDate>Sun, 17 Feb 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/02/17/misadventures-with-crm-2011-web-services-and-adfs/</guid><description>I think the Dynamics CRM 2011 SDK is swell for interoperability, but I wanted to get a closer look at how the actual web service calls work, so I decided to access the sandbox CRM instance my company provides using a WSDL-based proxy as described here. Because the SDK has several examples for connecting to CRM instances using different kinds of authentication in the SDK\SampleCode\CS\WsdlBasedProxies directory, I figured this would be a piece of cake.</description></item><item><title>Displaying FetchXML results with XSLT on the client side in a Dynamics CRM 2011 web resource</title><link>https://alexanderdevelopment.net/post/2013/02/11/displaying-fetchxml-results-with-xslt-on-the-client-side-in-a-dynamics-crm-2011-web-resource/</link><pubDate>Mon, 11 Feb 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/02/11/displaying-fetchxml-results-with-xslt-on-the-client-side-in-a-dynamics-crm-2011-web-resource/</guid><description>A few weeks back, I wrote a post that showed how to retrieve and display FetchXML using jQuery in a Dynamics CRM web resource. In that example, I used jQuery&amp;rsquo;s each() method to iterate through each result and append them to an HTML element on the page. Using each() is a good approach if you need to actually do something with each row, but if you just want to display data, XSLT is a much easier way to do it.</description></item><item><title>Better line charts in Dynamics CRM 2011 - part II</title><link>https://alexanderdevelopment.net/post/2013/01/27/better-line-charts-in-dynamics-crm-2011-part-ii/</link><pubDate>Sun, 27 Jan 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/01/27/better-line-charts-in-dynamics-crm-2011-part-ii/</guid><description>In part I of this series, I showed how to query Microsoft Dynamics CRM for aggregate data using FetchXML and then pass the results to Flot to generate a line chart. In this second part, I will expand on that to show how to query for and chart multi-series data. For my example today, I will be creating a chart that shows the number of contacts created by date and state (address, not statecode).</description></item><item><title>Better line charts in Dynamics CRM 2011 - part I</title><link>https://alexanderdevelopment.net/post/2013/01/24/better-line-charts-in-dynamics-crm-2011-part-i/</link><pubDate>Thu, 24 Jan 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/01/24/better-line-charts-in-dynamics-crm-2011-part-i/</guid><description>Earlier this week I posted an entry about using FetchXML and JQuery in a Dynamics CRM 2011 web resource. The reason I first started looking at those two together was that I wanted to see if I could generate better looking line charts than are available out of the box (spoiler alert: I did).</description></item><item><title>FetchXML + jQuery in a Dynamics CRM 2011 web resource</title><link>https://alexanderdevelopment.net/post/2013/01/21/fetchxml-jquery-in-a-dynamics-crm-2011-web-resource/</link><pubDate>Mon, 21 Jan 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/01/21/fetchxml-jquery-in-a-dynamics-crm-2011-web-resource/</guid><description>Over the weekend I started looking at a hobby project that involved querying and working with aggregate data from Dynamics CRM 2011 inside a hosted web resource using jQuery. Initially had I planned to use the OData/REST endpoint since that is much sexier than SOAP lately, but after a quick web search I realized that OData doesn&amp;rsquo;t support &amp;ldquo;group by&amp;rdquo; queries, so that left me looking at FetchXML.</description></item><item><title>Dynamically setting field requiredlevel attributes in Dynamics CRM 2011</title><link>https://alexanderdevelopment.net/post/2013/01/16/dynamically-setting-field-requiredlevel-attributes-in-dynamics-crm-2011/</link><pubDate>Wed, 16 Jan 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/01/16/dynamically-setting-field-requiredlevel-attributes-in-dynamics-crm-2011/</guid><description>One of the things I like best about the Dynamics CRM 2011 form object model is that it exposes the requiredlevel attribute for form fields, so you can dynamically set fields as required or not in response to user actions. This is great if you have different types of a single entity and business rules dictate that you must capture different data values for each type.</description></item><item><title>How to unit test C# Dynamics CRM interface code - part III</title><link>https://alexanderdevelopment.net/post/2013/01/13/how-to-unit-test-c-dynamics-crm-interface-code-part-iii/</link><pubDate>Sun, 13 Jan 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/01/13/how-to-unit-test-c-dynamics-crm-interface-code-part-iii/</guid><description>In parts one and two of this series, I gave an introduction to unit testing Dynamics CRM C# interfaces code with mock objects using NUnit and Moq, and I showed code samples for a couple of different scenarios. In this post I will show how to work with CRM metadata (optionset values, statuscode values, etc.</description></item><item><title>How to unit test C# Dynamics CRM interface code - part II</title><link>https://alexanderdevelopment.net/post/2013/01/09/how-to-unit-test-c-dynamics-crm-interface-code-part-ii/</link><pubDate>Wed, 09 Jan 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/01/09/how-to-unit-test-c-dynamics-crm-interface-code-part-ii/</guid><description>Earlier this week I wrote a post that gave an introduction to unit testing Dynamics CRM C# interfaces code with mock objects using NUnit and Moq. The sample code in that post was extremely simple, so I wanted to follow up with a more complex example that shows how to test multiple calls to the CRM web service instead of just a single one.</description></item><item><title>How to unit test C# Dynamics CRM interface code</title><link>https://alexanderdevelopment.net/post/2013/01/06/how-to-unit-test-c-sharp-dynamics-crm-interfaces-code/</link><pubDate>Sun, 06 Jan 2013 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2013/01/06/how-to-unit-test-c-sharp-dynamics-crm-interfaces-code/</guid><description>A while back I wrote a post that gave a high-level overview of some of the tools I had used at a previous job to do unit testing of Dynamics CRM interfaces code, but I didn&amp;rsquo;t get into the why or how. Here is an introduction to unit testing Dynamics CRM code using an automated unit testing framework and a mock object framework.</description></item><item><title>Simple C# class to populate datatable from FetchXML</title><link>https://alexanderdevelopment.net/post/2012/12/29/simple-c-class-to-populate-datatable-from-fetch-xml/</link><pubDate>Sat, 29 Dec 2012 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2012/12/29/simple-c-class-to-populate-datatable-from-fetch-xml/</guid><description>I&amp;rsquo;ve typically preferred to access Dynamics CRM data using SQL queries, so I have never worked much with FetchXML. I&amp;rsquo;ve recently started working on a bit of a hobby project where it makes more sense to populate a datatable from using FetchXML than to use a SQL query, but unfortunately I have encountered three differences between FetchXML and direct SQL that I don&amp;rsquo;t particularly like:</description></item><item><title>Dynamically setting field requirement levels in Microsoft Dynamics CRM</title><link>https://alexanderdevelopment.net/post/2011/03/21/dynamically-setting-field-requirement-levels-in-microsoft-dynamics-crm/</link><pubDate>Mon, 21 Mar 2011 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2011/03/21/dynamically-setting-field-requirement-levels-in-microsoft-dynamics-crm/</guid><description>In Dynamics CRM you may have a field you want to be required some of the time, but not required, or maybe not even enabled, the rest of the time. In this post I&amp;rsquo;ll show you how to dynamically enable/disable and set/unset the required attribute of CRM form fields using JavaScript.</description></item></channel></rss>