Now I can reliably connect to the CDS T-SQL endpoint and execute queries against it, I want to get the data into some objects for me to use. I currently use EntityFramework and Dapper for this in other projects, so I’ll take a look at those two.
CDS T-SQL endpoint pt 4 – Performance
A common question I’ve seen so far about the new CDS T-SQL endpoint is how it compares performance-wise to using FetchXML. After all, FetchXML is “native” to CDS while T-SQL might be viewed as the johnny-come-lately compatibility layer, so it’s going to be slower, right?
CDS T-SQL endpoint pt 3 – SqlClient
As a developer, the first thing I want to do with any new tool is try and integrate or extend it with my own code. This is always one of the real benefits of CDS and the Power Platform for me, as it’s so much more open to extensibility than Continue Reading
CDS T-SQL endpoint pt 2 – First Thoughts
Let me just say, this thing is going to be great. It’s the biggest advancement in the platform for some years, and I don’t think any competitor will come close. However, it is a preview feature, and it does have some issues. Hopefully some of these at least will get Continue Reading
CDS T-SQL Endpoint pt 1 – Connecting
The biggest announcement of MBAS for me by a long way was the new T-SQL endpoint. For those who missed it, go and check out the recordings.
D365UG UK: Data Integrity & Quality – Tips & Tools
A bit of a mouthful of a title! I had a great time earlier today presenting at my first ever virtual event, D365UG UK. Many thanks to the organising team for a smoothly run event!
SQL 4 CDS 2.0.0 released!
I’m very pleased to release version 2.0.0 of my SQL 4 CDS tool today! If you haven’t come across it before, SQL 4 CDS is an XrmToolBox tool to query and manipulate your CDS data using regular SQL queries, making it accessible to a much wider range of users. You Continue Reading
Inside FetchXML pt 10 – link-entity (again)
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
Inside FetchXML pt 9 – distinct
You can ensure your query only produces each row once using the distinct attribute. For example, if you have multiple entries for the same company name you can get the list of unique names using:
Inside FetchXML pt 8 – page, count & top
By default you’ll get up to 5,000 records that match your query. The top-level <fetch> element supports a few options to help you control this: