Query Panel
What this covers
The Query panel is a SQL workbench inside Model Builder. Paste a SQL statement, choose a dialect, validate it, explain the route, or execute it against the model. Use it when you need to test the query router directly instead of building a pivot in the Measure Query Panel.
Main controls
| Control | Purpose |
|---|---|
| SQL editor | Holds the raw query sent to the router. |
| Dialect | Tells the validator how to parse the query. |
| Force route | Optional override for source, aggregate, or pocket routing during investigation. |
| Persona | Runs the query as a selected persona so security and parameter filters can be checked. |
| Validate | Parses and checks the query without execution. |
| Explain | Shows the route and compiler trace without returning result rows. |
| Execute | Runs the query and displays rows, timing, route, and trace output. |
When to use it
Use the Query panel to reproduce a BI-tool query, debug routing, compare forced routes, inspect generated SQL, and confirm row-security behavior for a persona. Use the Measure Query Panel when the question starts from one model measure and a few dimensions.
Reading the route
The route trace explains whether Tessallite used an aggregate, a pocket table, or the live source. If the route is unexpected, run Explain first, then use Force route only for diagnosis.
Saving and reusing a query
A query you run often can be saved to the model's Saved Queries so you — and your teammates — can re-run it without retyping it. Give the query a name and an optional description and save it. Saved queries belong to the model, not to one person, so anyone with access to the model sees the same list and can run any of them.
Because the list is shared, changing or deleting a saved query is governed:
- You may always edit or delete a query you created.
- A Modeller (or higher) may edit or delete any saved query on the model.
- A Viewer who did not create a query cannot change or delete it — the panel shows the server's message ("Only the query owner or a modeler can modify this saved query") rather than failing silently.
Deleting always asks you to confirm first, because a delete cannot be undone and the query is shared with everyone on the model.