DASHBOARDS & GRIDS
Saved views as a workflow
Filter once, name it, come back to it every morning. A saved view is a question the dashboard keeps answering with current data.
- Open the grid, set status, set priority, set the date range
- Sort, scroll, check the count
- Tomorrow, do it again; a colleague does it slightly differently
- Open the view; the count is current
- Zero means nothing is waiting
- Everyone opens the same definition
The morning routine
Every operations desk has one. Open the orders screen, set status to urgent, set the due date to today, sort by customer, scroll, count. Then the rejected ones. Then whatever is waiting for review. Twenty minutes of clicking that produces three numbers, done slightly differently by each person who does it, and done again tomorrow. The routine is not the problem; it is a good routine. Rebuilding it by hand every day is the problem.
What a saved view is
A saved view is that routine captured once. Filter the grid down to what matters, give it a name - Urgent orders - and it becomes a thing you open rather than a thing you build. The filters are the definition; the name is the handle. On a dashboard the same idea saves the filter state of every widget at once, so a regional manager's view of the sales dashboard opens already narrowed to her region.
The difference from a bookmark or a favourite is that a saved view stores the question, not the page. A bookmark returns you to a screen; a saved view returns you to a set of conditions and asks the data what matches them now. That is why it can be shared without being copied, and why it still works after the collection has been refreshed a hundred times.
Why "current" is the whole point
A saved view is not a snapshot. When you open it, the record count reflects the latest indexed data: 14 urgent orders this morning, 36 rejected, 0 awaiting review. The zero is as useful as the fourteen, because it says nothing is waiting and the morning can move on. A screenshot from yesterday could not say that. The view is a question - "what matches these conditions now?" - and the index answers it fresh each time, as of its last refresh, which is why the refresh schedule for the orders collection is the operations desk's schedule and not the finance team's.
From a view to a workflow
- FilterNarrow the grid to what matters.status = urgent · due today
- Save by nameThe filters become a view.Urgent orders
- OpenThe count reflects the latest indexed data.14 · as of 09:00
- ActWork the list; zero means done.0 awaiting review
- ShareA colleague opens the same definition.same view, same count
Filter, save by name, open, act, share. The first two happen once. The third and fourth happen every day, and the fifth is what makes the view an organizational object rather than a personal one: when a colleague opens Urgent orders, they get the same definition and the same count, not their own interpretation of "urgent". A set of saved views is, in effect, the team's agreed list of what needs attention, maintained by the data instead of by memory.
The workflow scales past one desk. A regional manager keeps a view per store; a finance analyst keeps a view per customer segment; a support lead keeps the view of orders with a complaint attached. Each is a question that person owns, answered fresh each morning, and the set of them across a company is a map of what the company watches. When a question stops mattering, the view is deleted, and nothing else has to change.
There is also a quieter benefit: saved views make the definitions visible. Open the view's filters and you can see exactly what "urgent" means to the operations desk. That is the kind of agreement that otherwise lives in people's heads and surfaces only when two of them disagree.
Saved views and dashboards
Saved views are the bridge between a dashboard and a report. They give a live view the reliability of a report - the same definition every time, by name - without freezing it. A dashboard with a handful of well-named saved views serves a dozen roles from one build: the North view, the this-quarter view, the wholesale-only view. Dashboard vs report looks at what a saved view does not replace, which is the document that has to be sent and kept.
Saved views also make handovers survivable. When the person who ran the morning routine leaves, the routine used to leave with them: which filters, in which order, what counted as urgent. With saved views the routine is on the screen, named, and the next person opens the same three views on their first morning. The knowledge moved from a head to the system, which is where operational knowledge should live.
And they make the refresh schedule visible in a useful way. A saved view that says as of 09:00 tells the person opening it at 09:40 that the orders placed in the last forty minutes are not in it yet. That is an honest number, and an honest number is one people keep trusting.
Naming them well
A saved view's name is read far more often than its filters, so name the question, not the mechanism: Urgent orders, not status=urgent AND due≤today. Keep the list short enough to scan; a desk with forty saved views has recreated the problem it solved. And when a view's count sits at zero for weeks, retire it. The list of saved views should look like the list of things the team actually watches, because that is what it is.