Dashboard referenceReference
Every row on a Report_ sheet describes one widget. These are the columns a row can use:
| Column | What it does |
|---|---|
| Widget | What kind of widget this row builds: kpi, chart, pivot, table, filter, measure or title. |
| Title | The heading shown on the tile — translatable through the Translation_ sheet. A chart names itself from its current picks (“Revenue by Region”), so a chart's Title cell isn't shown. |
| Form / Section | Which form's records the widget reads. On a form with line items, it also says whether to read the header or the LINE ITEMS. |
| Measure / Aggregate | What to add up: a field, or * to count rows — and how: sum, average, count, distinct count, min, max, median, % of total or % of group. A pivot can list several, comma-separated. |
| Rows / Columns | How to slice the numbers: group by these fields, comma-separated to nest (region, then salesperson). A date can bucket into periods: order_date by month (also quarter / year). For a flat “table”, this cell instead lists which columns to show. |
| Chart | For a chart widget, the shape of the graph: bar, line, area, pie or donut. |
| Filter | Keep only the records you want — for example status = 'Shipped'. Write conditions the same way as on the Rules sheet. |
| Width | Optional: how wide the widget sits on the 12-column grid — a number (1–12) or full / half / third / quarter. Left blank, each widget type takes a sensible default. |
Header vs. line items. A sales order has one header (customer, date) and many lines (products, amounts). The Section column says which of those a widget counts: a header section gives one row per record; LINE ITEMS gives one row per line. A line-level measure can still be grouped by a header field — revenue by region works. The reverse would inflate your totals: a header amount repeats on every line, so in the line view header fields only group, never total. On a form with several line grids, name the grid itself (PART LINES) — the plain line items name is ambiguous there. A header-grain widget can also total one grid per record with amount from PART LINES.
Derived dimensions. You can group by things that aren't on the form. Pull an attribute through a master-data field — category from product slices orders by each product's category — or use part of a date: year from order_date (also quarter, month, day). Derived fields work everywhere: as flat-table columns, in the filter bar, and in the viewers' group-by pickers.
The filter bar. Viewers can narrow the whole page to, say, one region or one month — any header dimension works. Add a filter row (naming fields in its Columns cell) to choose which fields appear by default. Viewers can still add or remove fields themselves, and long value lists get a search box and Select all.
Several dashboards. Each Report_ sheet becomes its own dashboard page, shown as tabs in the order the sheets sit in your workbook.
Adding, changing & deleting. Dashboards live in your workbook, so there's no separate designer to learn: edit the sheet and re-upload through Change app. A new Report_ sheet adds a dashboard; removing the sheet deletes it.
Every viewer sees their own language. Titles translate through the Translation_ sheet (Object Type widget, report or measure), dropdown values through the List_ language columns, and every number, date and currency is formatted for the viewer's region.