Key finding: every filter/slicer is client-side on top of the snapshot — it never becomes SQL. That has three good consequences: zero cost per interaction, no injection surface through slicers, and the limit becomes what's in the snapshot. Examples use the synthetic workspace Comércio Aurora Ltda.
Slicers (8 types) and scopes#
- What it is — 8 slicer types:
select,daterange,buttons,range,hier(cascading),number("what if"),field(field parameter) andmeasure. - When to use it — slice the dashboard by category, period, range; or swap field/measure (field/measure) and simulate a number (number/what-if).
- How it works — each slicer has a scope: dashboard, page or per
visual (target); search in the filter (≥20 options), multi-select (OR/AND),
select all/clear. Sync across pages (
syncPages): a control on one page applies to the whole dashboard. - Prerequisites — a snapshot with the columns used by the slicer.
- How to validate — add a
selectonprodutos.categoriascoped to the dashboard, select "Bebidas" and confirm every visual slices; change the scope to a single visual and confirm the warning when it "doesn't reach anything". - Limits and caveats — personal per-user filters (personal slicers) are
Roadmap; what exists per user is RLS (see Security). Slicers operate on the snapshot, not on the live source. - Sample data (synthetic) — categories {Bebidas, Limpeza, Higiene}; selecting "Bebidas" leaves only revenue=250.
- Evidence (code/test) —
DASH_FILTER_TYPESindashboard-widgets.ts; renders indashboard-filters.tsx; slicer tests.
Relative dates#
- What it is — period presets: today, 7d, 30d, month, year, and the generic
-Nd/-Nw/-Nm/-Ny(Power BI style), in the dashboard's time zone. - When to use it — a "last 30 days" that moves forward on its own every day.
- How it works —
presetRangecalculates the window in the dashboard's configured time zone. - Prerequisites — a date column in the snapshot.
- How to validate — set "last 30 days" and confirm the range shifts when you change the reference date.
- Limits and caveats — it depends on the dashboard's time zone (America/Sao_Paulo by default).
- Sample data (synthetic) — today=2026-07-31 → window 2026-07-02..07-31.
- Evidence (code/test) —
presetRange(dashboard-widgets.ts) + test.
Cross-filter / cross-highlight and the interactions editor#
- What it is — clicking a visual highlights the selection and slices the others; plus a source→target interactions editor to define, per pair of visuals, whether the action is Filter / Highlight / Ignore.
- When to use it — the gesture that "feels like Power BI": click a bar and see the rest of the dashboard react.
- How it works — a click applies cross-filtering (Ctrl accumulates; clicking again clears); the pairs editor sets the mode per target, inheriting the global mode ("default") with an in-memory preview before saving; sanitization with an allowlist (valid modes, existing ids, no self-reference, a ceiling on pairs). The same semantics apply in the authenticated viewer, the public view and embeds.
- Prerequisites — two or more visuals on the page.
- How to validate — in the interactions editor, set "Category bars → Table = Filter"; click a bar and confirm the table slices; switch to "Ignore" and confirm the table doesn't react.
- Limits and caveats — persistence of the selection across sessions is partial (see below).
- Sample data (synthetic) — clicking "Bebidas" on the bars filters the table to the Bebidas items.
- Evidence (code/test) —
interactions-editor.tsx,interactions-sanitize.ts+ test;applyCrossFilter(dashboard-widgets.ts);dashboard-view.tsx.
Drill-down / drill-up#
- What it is — going down/up levels through a column hierarchy and through dates (year → month → day).
- When to use it — exploring from "Region" down to "City", or from year to day.
- How it works —
config.drillover the hierarchy; context chips + a drill-up button; dates usedateBucket. - Prerequisites — a hierarchy defined in the model (see Semantic model).
- How to validate — on a visual with the hierarchy
Região > UF > Cidade, click to go down from Sudeste to São Paulo and use drill-up to go back. - Limits and caveats — drill operates on the visual's snapshot.
- Sample data (synthetic) — Sudeste → SP → São Paulo.
- Evidence (code/test) —
config.drill(dashboard-widgets.ts),dashboard-filters.tsx.
Drill-through between pages#
- What it is — jumping to another page carrying the context (by column), automatically on click or via a button, with a "back" chip.
- When to use it — click a product and go to that product's detail page.
- How it works —
DashPageTab.drillthroughdefines the key column; the target opens filtered by the clicked value. - Prerequisites — a target page configured as a drill-through target.
- How to validate — set "Product detail" as the target by
produtos.id; click a product in the overview and confirm the detail page is already filtered. - Limits and caveats — the context passed is per configured column.
- Sample data (synthetic) — clicking product id=10 opens "Detail" with
produto_id=10. - Evidence (code/test) —
DashPageTab.drillthrough,dashboard-filters.tsx.
Tooltips and tooltip pages#
- What it is — tooltips with extra fields, rich tooltips (content beyond the number) and tooltip pages (a whole dashboard page used as a tooltip, Power BI style).
- When to use it — showing details on hover without cluttering the visual.
- How it works —
config.tooltipFields/tooltipPage; the tooltip page is hidden from the tab bar and appears when you hover over the point. - Prerequisites — extra fields and/or a page marked as a tooltip.
- How to validate — add
produtos.marcaas a tooltip field and confirm it appears on hover; create a tooltip page and confirm the preview. - Limits and caveats — a rich tooltip is structured content; the data engine is the same as the source visual's.
- Sample data (synthetic) — a "Revenue by category" tooltip showing brand and number of orders.
- Evidence (code/test) —
dashboard-tooltip.ts(+15 tests),tooltip-rich.ts+ test.
Bookmarks#
- What it is — up to 10 bookmarks that save the dashboard's complete state, applicable via a button.
- When to use it — saving an "executive view" and a "detailed view" and switching with one click.
- How it works — the bookmark saves selections/filters/state; a button can apply it.
- Prerequisites — a configured state to save.
- How to validate — set filters, save as a bookmark "July", change everything and apply the bookmark to restore.
- Limits and caveats — bookmarks belong to the dashboard, not to each user.
- Sample data (synthetic) — bookmark "Bebidas · July".
- Evidence (code/test) —
saveBookmarksAction,dashboard-filters.tsx.
Persisting and sharing selections via URL#
- What it is — the selection travels in the URL (
?f=, base64url) so you can share a filtered view. - When to use it — sending an already-filtered link to a colleague.
- How it works — the URL stores selection + date; parameters (field/measure/what-if) also travel through the state codec.
- Prerequisites — filters/parameters applied.
- How to validate — filter "Bebidas", copy the URL, open it in another tab and confirm the filter is restored.
- Limits and caveats — range/hierarchy don't survive through the URL alone (they depend on a bookmark); there's no per-user autosave.
- Sample data (synthetic) —
?f=…with category=Bebidas, period=July. - Evidence (code/test) —
dashboard-filters.tsx(?f=),url-state.ts.