<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>fetchxml on Alexander Development</title><link>https://alexanderdevelopment.net/tag/fetchxml/</link><description>Recent content in fetchxml on Alexander Development</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 12 Mar 2018 15:00:00 +0000</lastBuildDate><atom:link href="https://alexanderdevelopment.net/tag/fetchxml/index.xml" rel="self" type="application/rss+xml"/><item><title>Updated solution for scheduling recurring Dynamics 365 workflows</title><link>https://alexanderdevelopment.net/post/2018/03/12/updated-solution-for-scheduling-recurring-dynamics-crm-workflows-2/</link><pubDate>Mon, 12 Mar 2018 15:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2018/03/12/updated-solution-for-scheduling-recurring-dynamics-crm-workflows-2/</guid><description>I&amp;rsquo;ve released an updated version of my recurring workflow scheduler for Dynamics 365 Customer Engagement. This solution targets Dynamics 365 version 9, so it should work in all current Dynamics 365 online organizations. You can download version 1.3 of my solution from here: https://github.com/lucasalexander/AlexanderDevelopment.ProcessRunner/releases/tag/v1.3.
For more information on the use of this tool, take a look at the original blog posts:</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>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>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>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>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>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></channel></rss>