I’m very proud to have some more of my contributions included in the latest release of the popular FetchXML Builder tool!
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
I’ve looked at different ways of accessing CDS metadata recently, but there’s another way I’d overlooked – using FetchXML. CDS exposes a limited amount of metadata as special virtual entities that lets you query it using standard FetchXML syntax:
I was very pleased today to see a new feature in FetchXML – column comparisons! This allows us to build queries that compares the values in one column against those in another. Previously we’ve only been able to compare a column against a constant value.
A follow-up on my previous post on link-entity, prompted by this tweet from Daryl LaBar: Was unaware of the new join operators. @jordimontana @XrmWizard have either of you used these, or know what they are supposed to do? The documentation is rather lacking…https://t.co/Nr4AyZMzb2 — Daryl LaBar (@ddlabar) April 2, 2020
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
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.
Along with some important updates to the existing SQL 4 CDS suite of tools, this release brings brand new integrations for SSMS 19 and Azure Data Studio!
I’ve just released SQL 4 CDS v6.3 with a number of useful improvements and fixes.