FetchXMLBuilder
FetchXMLBuilder copied to clipboard
rappen
Convert OData to FetchXML
OData / Flow ➡ FetchXML.
Get query:
- Paste full OData query
- Paste one/several parts from Flow Dataverse List rows parameter items
Create FetchXML from this.
Like the same as we have for FetchXML ➡ OData and Flow parameters.
It should be possible, but... are people writing queries in OData format first that need to be converted back? Just trying to understand the use-case.
Or is it more like:
- Write the query in FetchXML Builder
- Convert it to OData and copy it into your Flow
- Close FetchXML Builder & don't save the query
- Realise you need to edit the query in the Flow and don't want to touch the OData
Or easier: From anywhere you find OData (or the Flow List Rows with parameters, not a "full" OData) and start from that, and want to investigate the query in FXB, which is easier than in Flow - or wherever. And who knows why people would need it... 😉
In older projects we had xrm.sdk nuget with fetch xml queries and used fetch xml builder + sql 4 cds to verify if something went wrong.
Currently we're using Simple.OData.Client + our custom wrapper on that package to use that type of processing in communication with dynamics. So in our current flow we have only a OData URIs. We use additionally postman/IDE debugging/logs to review our requests that we sent. In my opinion OData-way is the most clean approach (the most minimized queries).
One use-case I often have is that I create the OData query in FXB to be used in a Cloud flow. Sometimes I get a changed requirement or have to change the request for some other reason. In that case, I would have to adjust the OData manually (merge old with new generated) or rebuild it in FXB to export a new version. If we could automatically convert it to FetchXML, do our changes and convert it back to OData it would save a lot of time.
