Skip to main content
A slice card is a dashboard card that reads a saved view through one line of grouping, filters, and measures. A regular card shows the result of the analysis that built the dashboard. A slice card follows the view instead. Rerun the views, and every card over them shows the new data without rebuilding the dashboard. Use slice cards when a dashboard should stay current on its own data. A new slice dashboard runs on its own Workflow, so each run brings the cards up to date without re-running the whole analysis.
Slice cards are available on select workspaces. Ask your Gravity contact to enable them.

Adding a Slice Card

Ask Orion in chat to add a card to a saved dashboard, or to replace one, and name the dashboard:
  • “Add a card showing weekly signups by channel to the Growth dashboard”
  • “Replace the revenue chart with revenue by region for the last 90 days on the Growth dashboard”
Orion answers the question from a view, then pins that exact line to the dashboard. The card shows the numbers Orion quoted in chat, because it reads the same line. A replaced card keeps its place and size on the dashboard. A card can also read a dataframe from a saved notebook directly, with no view in between. Such a card follows the notebook’s latest run, or stays pinned to one run. After Orion runs a notebook, it builds dashboard cards from its results as slice cards. A few cases still use regular cards, such as a very long list of raw rows or a first or last value. Orion checks that the new card renders before saving it. If the check fails, nothing is saved and Orion tells you why. The dashboard must already be saved, and you need edit access to its project.

What a Slice Dashboard Can Show

Ask Orion for a dashboard with tabs, and each tab gets its own filters, which apply only to the cards on that tab. A filter you set on one tab does not change the others. Ask for a row of headline numbers at the top of the dashboard, and Orion ties each one to a card. The number follows that card’s filters and shows “No value” when the card has none. Charts can be drawn as area charts. You can also ask for the latest or opening value of a measure, such as a closing balance. These read the view’s time column, so the view needs one.

Where a Time Window Ends

A windowed card ends at the view’s last complete period, not at its newest row. Rows that arrive late would otherwise draw a collapse that never happened. Where the view’s newest rows fall outside that last complete period, the Time window control offers Last complete data and Latest data. Last complete data leaves the newest rows out and keeps every period comparable. Latest data brings them back, at the cost of a final period that is still filling and reads low. The control is in Explore. A chart that reaches a period still in progress draws that last point dotted. A note underneath names the period and how much of it the data covers. A dip at that point is a partial period, not a fall.

Undoing a Change

Ask Orion to undo the last card change: “undo that change to the dashboard”. Each card Orion adds or replaces saves the previous version of the dashboard first, so undo restores it. Orion confirms which version it restored. Undo can itself be undone, because the version it replaces is saved too. You can also ask for an earlier version by its number. If someone else saves the dashboard while Orion is restoring it, nothing is restored and Orion asks you to retry.

Running a Slice Dashboard

Save a slice dashboard that belongs to a project and reads at least one data source. Orion creates a Workflow named after it and starts its first run right away. The Workflow has no schedule, so it runs when you ask. A dashboard saved before this gets its Workflow the next time it is saved, or sooner with Set up runs. A dashboard with a Workflow shows Run in its header, with the run history in the version rail. Run starts a new run. Each run keeps its own copy of the view results, so opening an earlier run shows its numbers as they were. You do not pin views yourself. Cards that generate their text, such as narrative and summary cards, are rewritten from each run’s data. A rewrite Orion rejects leaves the card’s previous text in place: see As a Workflow output. A dashboard without a Workflow shows Set up runs to editors. It attaches a Workflow, and the page switches to Run and the run history. Viewers do not see it.

Refreshing a Dashboard Without a Workflow

On the page of a slice dashboard that has no Workflow, Refresh sits in the header. It reruns every view the cards read, inputs first, so a view built from another view gets fresh inputs. While it runs, the button reads Refreshing with a count of views done, and cards over a view in progress show a Refreshing badge. When the refresh finishes, the cards update on their own. You do not need to reload the page. Beside the button, everyone who opens the dashboard sees when it last refreshed, for example Updated 5m ago. After a partial or failed refresh it reads Refreshed with errors 5m ago, in amber. Hover it to see what happened to each view. A refresh skips two kinds of view:
  • Fresh views: a view that ran in the last five minutes is reused, not rerun
  • Pinned views: a view pinned to a particular run stays as it is
You can also ask Orion in chat: “refresh this dashboard”. Orion waits about a minute and a half for the result. A longer refresh keeps running, and the cards update when it finishes. If the data looks wrong even though it ran recently, say so, and Orion reruns the fresh views too. A dashboard built from notebook results hands off instead. Refresh starts the dashboard’s Workflow, and the page treats it as it does after Set up runs: it switches to Run and the run history, and the new run is watched there. This page does not wait on the refresh itself. A dashboard that is a Workflow output has no Refresh button. Its Workflow’s runs keep it current. A new slice dashboard with a project and a data source is one. A dashboard whose cards read more than 16 views cannot be refreshed. Nothing runs, and Could not refresh says so.

When a refresh fails

After an hour the page stops watching a refresh, though the refresh itself may still be running. Hover Refresh to see that the page stopped watching, and reload the page to see the refresh’s status. Viewers have no button, so they see nothing and should reload.

Exploring a Card in the Workbench

Hover over a slice card and select Explore. The dashboard opens a Workbench tab with that chart. The Dashboard tab stays as it was, with its filters, so you can switch back at any time. Charts built from a notebook can be explored too. Above the chart sit a Chart type picker and a Legend switch. The picker offers the types the current grouping can draw, so its choices change as you regroup. The Workbench only reads. It never changes the dashboard: the chart type, the legend, and every other control here move the chart in front of you alone. To change the card itself, select Edit and edit the chart card.
The Workbench and Advanced mode are available on select workspaces. Ask your Gravity contact to enable them.

Drilling in

Select a bar or a point to drill into it. The chart narrows to that member and groups by the next field. On a date, it steps down to the next smaller period. A breadcrumb above the chart shows the path, starting with the card’s title. Select any step in it to go back. Back to the card returns the chart to the card as the dashboard shows it.

Advanced mode

Turn on the Advanced mode switch beside the Workbench tab. The slice panel slides in with a Fields panel and the same shelves described below, so you can regroup the chart by hand. The switch is off when you open the page, and it stays as you set it while you explore other cards. If a card has no slice to edit, the switch is disabled and its tooltip says why. Comparison and drivers opens the controls for asking what changed:
  • Compare: Off, Prior window for the span just before your time window, or Previous run for the run of the Workflow before this one. Prior window needs a time window. Previous run needs at least two runs
  • A row of earlier runs, shown by date and ending at Latest: pick one to compare with it. It appears when there are earlier runs
  • All N runs, where N is the number of runs, up to 8: shows the slice as each recent run reported it, which reveals late data and restated numbers
  • Drivers: after you pick a compare, Orion ranks the fields that best explain the change and names the members that moved the number most. Select a field to break the change down by it. Pick by hand lets you choose the fields yourself under Explain the change by, and Back to ranked returns to the ranking
Expression shows the slice line behind the chart, for reading or editing by hand. It stays hidden until you ask for it, and Hide expression puts it away again.

Chat beside the Workbench

Ask Orion in chat to filter or regroup the chart. The chart and the Advanced controls update together when Orion answers. Each chart Orion produces is saved as a version, and the chart version control steps between them. Your manual edits are temporary. Orion sees them with your next message, but they do not return after a reload. Above the chat message box, a card shows your latest saved exploration, with a thumbnail of the chart and how many versions are saved. Select Open workbench to reopen the dashboard and the Workbench side by side, with the same conversation and the latest chart. Pick an earlier version and send a message to continue from it. The card is hidden while that Workbench is open. Dismiss it with the close button and it returns on your next visit. People you share the conversation with can browse its saved versions without changing them.

Exploring a Slice

Explore is also a workspace for reshaping a slice by hand outside the dashboard. It opens from a slice result in chat with the icon (its tooltip reads Open in Explore), and from a view’s detail sheet with Explore. When the answer itself is a chart Orion designed, a report, a dashboard, or a slide deck, the slice result folds into the collapsed work row above the answer, the row that reads Worked for or a count of tools used. Open that row to reach the icon. On a dashboard, Explore on a card opens the Workbench instead. Drag fields from the fields panel onto the Values, Rows, Columns, and Filters shelves. A field on Rows groups the result, and one field on Columns pivots it. Move a field between shelves by dragging it, or from its menu with Move to Columns or Move to Rows. Pick a chart type, and set the time window and the comparison period from the controls that read All time and No comparison until you change them. Hover them to see Time window and Compare. Undo, redo, and History step back through the versions of this session. Explore does not save to a dashboard. To keep what you built, send it to Orion with Send to Orion, or Continue in chat from a view, and add a note. Orion receives the slice line and the view, not the rows. Then ask Orion to add it to a dashboard. Copy, then Copy expression, puts the line on your clipboard instead.

Who Can Use It

  • Analysts and Admins: add, replace, and undo slice cards, run or refresh slice dashboards, set up runs, and open Explore
  • Viewers: read slice cards and see when the dashboard last refreshed. Refresh and Set up runs are not shown to them. On a shared dashboard page, Explore on a card shows only where the project turns on Extended Viewer Settings