45 ms·
That's because, functionally, that sort of interaction does not belong on a dashboard. Dashboards are meant to succinctly summarize what's going on under the ho
by rrrx3 13y ago
That's because, functionally, that sort of interaction does not belong on a dashboard. Dashboards are meant to succinctly summarize what's going on under the hood. "Bakery 47 is running low on cinnamon rolls" && "Coffee shop on Main is your #1 seller this week" - Rolling up your sleeves and manipulating that data is best done in a bespoke screen/view.
- est 13y agodashboard is only a subset admin templates They are mostly read-only, useful for OLAP data. Admin templates are useful for OLTP data.
- ricricucit 13y agoi agree
- rrrx3 13y agoThat doesn't address use cases. A Dashboard is the first thing a user sees. If it's not, you're doing it wrong. Furthermore, in-depth slicing & dicing of data, manipulation, etc, should always be done in bespoke screens, not on a dashboard. Combining that stuff with an analytical view that the dashboard provides leads to kludge. Every single time.