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 click goes one place, not both
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 a login.
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.
Nobody builds a chart that misreads its own numbers, or finds that out on the wallboard. Columns, funnels, treemaps, radar, scatter, gauges and pivots.
Agents down the side, weeks across the top, and the number you care about in every cell. The shape finance asks for when a chart will not settle the argument.
A board on the wall gets read from across the room. Anything under target colors itself as the chart is painted, so a supervisor sees it without stopping.
The number that was promised, drawn across the same chart as the number that arrived, so the floor reads itself against its target, not yesterday's bars.
Nobody has to remember what last week looked like, or dig out the sheet it was written on. The same figure is counted again over the window before it.
The report that needs two exceptions and a date range stays one widget, instead of three tiles that nearly agree. Seventeen operators in a nested and-or tree.
Ten thousand plus never turns up before two hundred on a board the floor is watching. Group by day through year, by equal bands, or by breakpoints you set.
Six palettes, one a print set for the pack that goes in front of a client. Pin one to a tile and the series, axis, grid and tooltip all move together.
Send a client the board without giving them a login. The address works until the day you name, dies the moment you revoke it, and leaves a row explaining why.
A figure on the screen where the work happens, not on a board somebody must remember to open. Built once, worked out against the records of whoever opens it.
How many calls, how many answered, how long they ran, how many missed, counted off the records the switch already wrote. Not a sample or last night's 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