One common pattern of queries I see about FetchXML is how to write queries to ask two different questions about the same related entity. For example: Invoices that include product A AND product B? Contacts that have pending emails AND no sent emails? Visits that have a page view of Continue Reading
Last time I looked at aggregates, but unforgivably I missed out how to apply grouping to date/time attributes:
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 Continue Reading
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.
I’m very proud to have some more of my contributions included in the latest release of the popular FetchXML Builder tool!
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>!
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.
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.
MSDyn365 MVP Jonas Rapp threw down a challenge on Twitter last week: True, I’ve been ignoring for too long…If you know some C# and some #MSDyn365 WebAPI queries – please help…! 😊Pull Requests accepted! https://t.co/7iHp6XzQbf — Jonas Rapp ᴹᴠᴾ 🇸🇪 (@rappen) March 4, 2019