Category archives: MSDyn365

Last time I looked at aggregates, but unforgivably I missed out how to apply grouping to date/time attributes: Not to forget – data grouping….! 😉https://t.co/pLqQo35mc3 — Jonas #LazyDev Rapp ᴹᴠᴾ 🇸🇪 (@rappen) December 18, 2019 Grouping works quite simply for data types such as text, picklist or lookup values, but a simple grouping of date/time […]

One feature of FetchXML that sets it apart from other CDS query options is aggregates. This is the option to get summary data (number of records, sum of opportunity value etc.) rather than the individual values from each record. If your only concept of how many records you have is “5,000+” then this is for […]

It’s often important to sort the results of your query, and in FetchXML you can do this with the <order> element. This is equivalent to the ORDER BY clause in SQL. Sorting by multiple fields By adding more <order> elements, the results will be sorted by each attribute in sequence. The orders are applied, well, […]

I’m very proud to have some more of my contributions included in the latest release of the popular FetchXML Builder tool! There are two main updates I’d like to show you: Live Updates As you edit your query, everything else now updates in real-time. No more clicking away to see your changes reflected in the […]

So far we’ve looked at using the <attribute> and <link-entity> elements to control what columns to include in your query, but for a truly useful query you’ll likely want to select which rows to include instead of taking everything. Enter <filter>! Filter or Condition? A <filter> is a group of individual <condition>s. Each condition applies […]

To combine data from different records in your query you need to use the <link-entity> element. This is equivalent to a join in SQL. Each <link-entity> needs 3 key pieces of information: The entity type to link to The attribute in the main entity to join from The attribute in the new entity to join […]

As promised, I’m starting a series of blog posts covering various aspects of FetchXML and the humble <attribute> element seems like a good place to start. The purpose of running a FetchXML query is to get some data back, and the <attribute> element defines which attributes get included in the result. You can add as […]