One number
Chart
A single figure for the whole table — a count, a sum or an average — with no axis.
When to use
Section titled “When to use”The answer is one number: how many open tickets, total revenue this month. Takes one series; a target turns it into a comparison.
When not to use
Section titled “When not to use”The reader needs to see how it changes — use a line or bars.
What the table needs
Section titled “What the table needs”Nothing beyond the rows; a sum or an average needs a number column.
Asking the AI
Section titled “Asking the AI”Describe it in a sentence — for example “how many deals are open”.
From another AI
Section titled “From another AI”An assistant connected to Routario over MCP (Claude, ChatGPT) makes it with chart_create, then puts it on a board with dashboard_tile_add.
Settings
Section titled “Settings”- Subtitle — One line under the title. What the reader should take from it.
- Series — Each series is one measure, optionally narrowed to the rows that match a condition.
- Measure — What each series computes over the rows in a slot.
- Unit — For ‘time between two dates’: the unit the gap is measured in.
- Aggregate — For ‘time between two dates’: how several rows’ gaps become one number.
- Where — Narrows one series to the rows matching a condition — how several series share one axis.
- Colour — A plain colour picks a pigment and says nothing about the data. A named meaning — went well, needs attention, went wrong — tells the reader something they will believe.
- Show numbers as — How the value axis, the tooltips and the printed values spell a number.
- Targets — A flat line at a goal, a floor or an SLA the chart is judged against. Not something the data produced.
- Good side of the target — Which side of the target is good — it colours how far a number is from it.
Auto-generated from the tile registry (core/custom_tables/tile_registry.py) — the same text the chart editor and the AI drafter read. Do not edit by hand.