Sheets
Spreadsheet modelling built on a governed query result — a familiar A1 grid with formulas, formats, multi-tab workbooks, and real-time collaboration.
A sheet is a spreadsheet built on top of a query result. You get the familiar A1 grid — formulas, cell references, number formats — layered over data that still comes from your governed semantic model. It is where analysts do the last mile of modelling that does not belong in the warehouse.
#What a sheet is made of
Following spreadsheet modelling (ADR-0018), a sheet combines three things:
- A bound range. The left-hand columns are the rows and columns of a saved exploration — the same governed result you would get in Explore. Refresh it and the data updates against the current model version.
- Calculated columns. Expressions defined over the bound fields. Because they are set-oriented, they can round-trip back to warehouse SQL.
- Free A1 cells. Anywhere outside the bound range you can write ordinary
spreadsheet formulas —
A1and$A$1references, ranges, and a broad function library.
#Working in a sheet
Open Sheets at /app/sheets, create a workbook, and bind a tab to an
exploration. From there you can:
- Write formulas and functions.
- Organize work across multiple tabs that reference each other.
- Apply editing features — formats, sort, filter, find & replace, insert/delete, undo/redo.
- Export to CSV or Excel.
- Collaborate in real time with presence and version history.
Note
Governed values from the bound range are always visible and findable, but you cannot overwrite them — the semantic model stays the source of truth.