01Edit FetchXML
Paste FetchXML from a Dataverse view or start with an example. Red underlines and gutter markers locate the first syntax or structural error. Hover a marker for details, or press Ctrl+Shift+M (⌘+Shift+M on Mac) to open the problems panel. Format the XML with Ctrl/⌘+Shift+F. The editor preserves nested filters, link-entity joins, aggregates, aliases, grouping, and other FetchXML constructs.
02Test in your environment
Paste your environment, app, or full Web API URL and the table’s exact EntitySetName. The tool extracts the environment host (including .api hosts) and uses API v9.2. Sign into that environment in another tab, then open the generated Web API URL. Dataverse executes the read request using your own permissions. The response opens on Microsoft’s domain.
03Import results
Copy or save the returned JSON and import it here. Search and sort records, switch between formatted and raw values, and export CSV or JSON. Only 50 rows render at a time; exported files include all imported rows.
Does this validate every FetchXML query?
Local checks catch malformed XML and common structural issues. Only Dataverse can validate your table metadata, supported operators, permissions, and execution limits. A structural pass is not a promise that the server will accept the query.
Can I use custom tables and advanced queries?
Yes. Enter the table’s actual EntitySetName; it is not always the logical name with an “s” appended. Write advanced features directly in XML. The request launcher preserves your query and URL-encodes it once. GET URLs longer than 32 KB require another client with batch support.
How do I get more rows?
Use count and page with a stable order. Standard Dataverse pages support up to 5,000 records; elastic tables use up to 500. Do not combine top with paging. For large datasets, use the server’s paging cookie in the next request. This free workspace imports one response page at a time and does not fetch additional pages automatically.
Where is my data stored?
Query text and imported results remain in this browser tab’s memory. They are not sent to the portfolio server or saved automatically. Opening a request sends the query directly to your environment and may put it in that browser tab’s URL history. No credentials or access tokens are requested here.
Microsoft FetchXML documentation ↗ · Paging guidance ↗
Connect GitHub Copilot to Dataverse MCP and call a Custom API ↗
Back to workspace ↑