💡Tip: Convert FetchXml to a Query expression

by Jul 8, 2024

💡Tip: Convert FetchXml to a Query expression

Have you had a situation where you have a FetchXml query, but you needed to inspect, tweak, or extend it a little?

You can load it into a XElement or XDocument and fiddle with it.

But you can ask Dataverse to convert your FetchXml query to a QueryExpression, just by making a request with FetchXmlToQueryExpressionRequest.

The response will contain a QueryExpression that you can inspect, tweak, and extend.

Btw. If you need to convert it back, there is also a QueryExpressionToFetchXmlRequest.

#
Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

The Trade-off Between Budgets and Quality ⚖️

The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more