2026-07
Tables, export and dashboards
Every table moved onto one engine with filtering, multi-level sort and saved views; a styled Excel export landed beside CSV; and dashboards became user-built.
- Published
Highlights
- One table engine — per-column filters, multi-level sort, row selection and bulk actions
- Saved views, shared across the team and authored by administrators
- Styled Excel export beside CSV, on every table
- Multiple user-built dashboards
This release is almost entirely about reading data — in tables, in exports and in reporting.
One table engine
Every table moved onto a shared engine: per-column filters with operators, multi-level sort, paging, and row selection for bulk actions.
Two rules hold across all of them and are worth knowing:
- Selection stores keys, not rows. Rows are replaced on every refetch, so holding references silently drops the selection.
- "Select all" means every filtered row across all pages — not the ones currently on screen.
Saved views
A named filter-and-sort combination, shared by every user and written by administrators only. The split is deliberate: how the team reads the data is a team decision rather than a personal preference.
Styled Excel export
Beside the existing CSV export. It matters mostly for dates: they are written as real dates rather than text, so they sort. The sheet opens in the correct reading direction with the header frozen.
Dashboards
A dashboard is no longer one fixed screen. You can keep several, build each from widgets, and resize and reorder them.
[VERIFY] — versions here are calendar-based (YYYY-MM) and name the month the scope closed. If a different numbering is already in use with customers, align to it before publishing.