The latest addition to FetchXML is Late Materialize. Turning this on or off doesn’t change the results of your query, but it does change how it’s executed behind the scenes, which could lead to some performance improvements.
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 received a notification today that the preview TDS endpoint had been disabled on my environment because of a security vulnerability.
I’ve been studying lately for the Azure Data Engineer Associate certification, and the main point of one of the exams (DP-201 – Designing an Azure Data Solution) is all about picking the data platform(s) that best meet the requirements. Having used SQL Server for many years it’s a simple trap Continue Reading
One of the things that really attracts me to the D365 platform is its metadata capabilities. As an ISV we make a lot of use of this at Data8, making sure our solutions automatically adapt to the customizations that each customer has made in their own system. There are a Continue Reading
I’m pleased to release the latest update for SQL 4 CDS today! For this update I’ve focused on common problems I’ve seen people encounter with their queries from my telemetry. These updates should either mean that more queries can be executed immediately, or the error message is more descriptive to Continue Reading
I’ve been doing some work today on filtering multi-select optionset fields in SQL 4 CDS and using the T-SQL endpoint, and I came across a few interesting quirks.
One great option in FetchXML is to filter dates using a relative filter such as “this week”, “older than 2 years” etc. This is particularly helpful when you build a view, as it will automatically build the date criteria each time so your view is always up to date.
Matt Beard & I spent some time investigating the new asynchronous merging functionality today and how it impacts Data8 Duplicare (it doesn’t, Duplicare continues to work as normal). If you haven’t seen this already, when you merge two records you’ll now see the message: The selected records will be merged Continue Reading
I wrote a post a while ago looking at the performance of the T-SQL endpoint compared to using FetchXML. Now I’ve got a better understanding of how it works, I wanted to check if the same performance considerations I’ve previously encountered when working with the filtered views on-premise still apply.