The owner points at gross margin and asks which orders pulled it down. The picture does not move. Someone exports Excel again. Someone calls a store manager. The dashboard is in the room. The decision still goes back to people. If you cannot click, you cannot “ask downward.”
Drill-down is not the four words “supports drill-through” on a feature list. It requires keys that still exist: order number, work-order number, SKU, and store code must travel from the summary to the line. Messy master data forks halfway down; see Without master data, visualization lies. When each system hands you half an ID, see When every system calculates its own numbers, what breaks.
Some people say leadership should not look at documents. Leadership should not live in detail. They must be able to authorize an open when something is wrong. Otherwise “margin dropped” becomes an attitude lecture, not a close on three loss-making orders. Shipping a report and analyzing a problem are not the same; see Reporting vs analysis: which one is a data capability. A shop-floor screen is the same: a crew must open a work order from the backlog count instead of walking to the office; see How a shop-floor screen keeps crews out of the office.
Alerts without drill-down are more dangerous. A red light with nowhere to go gets ignored. Alerts must reach a person and carry a document link; see Alerts pushed to people, so exceptions rarely sit overnight. A decorative screen you cannot click is the same as doing nothing; see Buying BI as decoration is the same as doing nothing.
When DaXi accepts a dashboard, we walk a real weekly-meeting question: pick an exception KPI and reach a document in three to five clicks, or write clearly “this KPI has no detail source.” If there is no source, do not put it on the chart. Why you need a dashboard, see Why an operations dashboard is not optional. How a project runs, see From brief to launch: how a data project actually runs. To build the layer you can click, go to the Data service page and name the KPI that does not open today.
Backlog on a floor screen must open a work order too, or crews still walk. A tour globe can be a separate build. Do not occupy the drill path. On cost, drill-down is worth more than another screen; see What dashboards or a data platform cost, and how long they take.
Layer permissions. Do not turn off all detail “for safety”
Layer access: a store manager sees that store’s documents; HQ sees the roll-up and can drill when needed. Turning off all detail “for safety” forces people back to exports.
Write the drill path into the definition document, not only the front end. When you add a chart, reuse the same API. Do not write the query again.
Leadership worries that drilling “too deep wastes time.” The fix is layers: default to an exception list, not 100,000 rows. Every row on that list must open. A summary with no key cannot even make an exception list. Excel looks like it drills because someone hid a filter. When that person leaves, it dies; see Excel weekly reports break once you scale. When numbers still fail to match, check definition vs key first; see The system is live and numbers are still wrong. How to trace it.