Drill-Through
Some answers will not fit on the board that raised the question. A click can leave, carrying the value it was standing on, and the board it lands on opens already narrowed to that value.
The click leaves the board
step 3 of 5/dashboard?id=…&crossFilters=W3sibSI6ImFjY291bnRzIiwiZiI6InJlZ2lvbiIsInYiOiJFTUVBIn1d
- storeda reference to the operator's own board
- resolvedidentifiers of the copies inside a workspace
The reference is turned into the workspace's own copy before the first paint, so a destination authored once by the operator lands on the right board in every workspace that holds it.
Product figures from the platform’s own defaults - not customer averages
How it works.
Two settings make the hop
A destination board picked from the operator's list, and a mapping saying which field over there should receive the dimension value from over here. Without the mapping the click reuses the widget's own broadcast field as the receiving field.
It travels as a URL, not as memory
The clicked value is encoded into a query parameter and pushed through the router. The receiving board reads that parameter before its first paint and seeds its filter state from it, so nothing renders unfiltered and then jumps.
A destination takes the click away from siblings
When a widget has both a destination and a broadcast field, the destination wins and the siblings are left alone. One point cannot both narrow the board it sits on and leave for another.
Where the hop lands
The destination is stored as a reference to one of the operator's own boards, and the workspace route resolves it to the copy living in your workspace before the page paints. So the value arrives on the board that was named, already narrowed, rather than on whichever one happened to open last.
One moment in every number.
Every number passes through the same seven. Drill-Through is the lit one, and everything either side of it is a different page in this category.
- 01Query
what is asked, and of what
- 02Shape
the measure and the dimension
- 03Draw
the visual chosen for that shape
- 04Arrange
where it sits on a dashboard
- 05Filter
narrowing it after the fact
- 06Drill
going from the number to the rows
- 07Share
who else gets to see it
The specifics.
8 facts- Destination
- Picked from the operator's boards, held as a reference to one of them
- Carried
- The dimension value under the pointer, as a single equality
- Mapping
- Source dimension to destination field, authored per widget
- Sources
- Any visual drawn per row, which is the same set that emits a cross-filter click
- Landing
- The named board's copy inside your workspace, resolved from the stored reference before the first paint
- Payload
- Thirty-two conditions and four kilobytes on the link, above which nothing at all is read from it
- Return
- None. A board that receives a hop does not learn where it came from
- Not the same as
- Cross-Filtering, which keeps the click on the board and takes second place when both are wired
What this is assembled from.
A number on a dashboard was built somewhere before it was drawn. These are the parts it is made of.
More in Reporting & Analytics
12 capabilitiesSeven data shapes, twenty-two visuals, shareable without the portal.
Hand a board to a team or a CRM role, at read or at edit, by the person who built it. Roles outlive people, which is why a share points at one, not a mailbox.
Columns, funnels, treemaps, radar, scatter, gauges and pivots - offered only where the data shape supports them, so no chart can misread its own data.
Cross one dimension against another with row, column and grand totals - the shape a finance team asks for when a chart will not settle the argument.
Colour a number by the rule that matters - under target, over threshold, inside a band - so a dashboard reads correctly from across the room.
Draw the target on the chart itself, so performance is read against the number that was promised rather than against the shape of the bars.
Put a window against the one before it, or against the same window a week, month, quarter or year back, on a card as a difference or a chart as a series.
Seventeen operators in a nested and-or tree, so the report that needs two exceptions and a date range stays one widget instead of becoming three.
Group by day through year, by equal-width bands, or by breakpoints you set, each band carrying a sort key so the axis reads in bucket order.
Six palettes including a print set, pinned per widget, each carrying eight series colours plus the axis, grid, card and tooltip colours drawn around them.
Thirty-two bytes of entropy, an expiry you choose, revocation on the spot, and only the hash kept at rest, on a board that draws its figures for a reader.
Name a slot at the call site and one authored widget answers it everywhere inside the product, computed against the records of whoever is signed in.
Total calls, answered rate, average duration and missed calls, split by direction and outcome, over the call records rather than a sampled export.
The rest of the platform.
Five more categories, all on the same record and the same bill. Each card names three of its capabilities, so you can tell from here whether it is worth opening.
Reporting & Analytics
See drill-through on your own floor.
Thirty minutes, your numbers and your data. We will set drill-through up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included