Skip to main content
A view is a dataset Orion saves so that later work can build on it. A metric tracks a value you watch over time. A view holds the rows you work from. The join, the filter, and the cleanup happen once, not in every analysis that needs them. Choose a view when you need a dataset. Choose a metric when you need a number. Views are created in chat, listed with the project’s metrics, and shared across projects through the Metrics Catalog.

Creating a View

Ask Orion in chat for the dataset you want to keep, or save one an analysis already produced:
  • “Save this joined table as a view I can build on”
  • “Create a view of orders and customers for the last 12 months”
Orion validates a view before saving it. It runs the code against your real data and shows you the result. The view is saved only after you confirm.

Finding Your Views

Open the project’s Metrics page and select the Views filter, which lists views only. The All filter leaves views out, so a view you just created does not appear there. See Metrics for the rest of the filter bar.
The project's Metrics page shows saved view cards below the filter bar. A red outline highlights the selected Views filter.

Find saved datasets with the Views filter

Reading a View’s Result

A view opens in the same detail sheet as a metric, on the Profile tab. Profile summarizes each column: ranges, common values, and missing values. Table shows a preview of the saved rows rather than the whole dataset. The sheet offers no full-table grid and no CSV export, so to work with every row, bring the view into an analysis. When a rollup panel appears below the result, choose columns under Group by and pick a Measure. Orion aggregates every saved row, including rows outside the preview. Use it to check a view before you build on it.
A view's detail sheet shows the selected Profile tab, column summaries, and rollup controls. A red outline highlights the profile and the Group by and Measure controls below it.

Inspect columns and summarize a saved view

Slicing a View

A slice is one question asked of a view, written as a single line. It names the measures, how to group them, the filters, and an optional time window or comparison.
Slices are available on select workspaces. Ask your Gravity contact to enable them.
Ask Orion for a breakdown, trend, or period comparison over a view. Where it can, Orion answers with a slice rather than a notebook run. Before slicing, Orion reads the view’s frame: the grain of its rows, the fields it can group by, and the measures it can total. Orion works the frame out from the column profile of the view’s latest run. To slice a view by hand, open it from the Metrics page and select Explore in its detail sheet. Explore appears on table and view results that have run at least once, for people who can edit the view. Drag fields onto the shelves, then select Continue in chat to send the slice to Orion, in a New chat or one you pick. See Exploring a Slice for the controls. To drill into a card on a dashboard, see Exploring a Card in the Workbench. A slice from a view can become a dashboard card that follows the view. See Slice Cards.

When a Slice Ends Before Your Newest Rows

A view whose newest rows are still loading has an incomplete tail. Where Orion finds one, a slice with a time window or a comparison ends at the last complete period rather than at the latest data. A part-loaded week otherwise reads as a real fall. The Time window control in Explore then lets you choose between the last complete data and the latest data. See Where a Time Window Ends. Where the detection is wrong, ask Orion to set the day the view is complete through. For a view that loads without lag, ask Orion to stop the check.

Correcting What Orion Infers About a View

The frame comes from the column profile, so parts of it can land wrong. Ask Orion in chat to correct any of these. A view with more than one date column still gets one primary date, and date filters, windows and week(...) all follow it. Orion can pick the wrong one. Ask Orion to make the other column the view’s time column. A stored count reads as a number that adds up. A per-day distinct count does not: summing it across days counts the same person twice. Ask Orion to mark that measure as one that must not be summed. It then refuses :sum, :mean and :avg, so slice it with :max or :min, or at the view’s grain. Orion refuses the change while dashboard cards still sum that measure, and names those cards, so repoint them first. A numeric flag can land as a measure rather than as a field you group by. Ask Orion to expose it as a groupable field.

Reusing a View

A saved view becomes an input for other work:
  • Ask Orion to build another view or a metric from it, and the new one reads the view’s saved rows
  • Use the chat’s @ menu to select an available project view
Ask Orion to refresh a view when its data has gone stale. Orion runs the view’s sources and transformation again and adds the result to its history. The run, schedule, and history controls in the sheet work as they do for a metric: see Managing Metrics.

Sharing a View Across Projects

A view belongs to the project that created it. To let other projects build on it, add it to the Metrics Catalog. Open the view from the Metrics page and select Add to catalog in its detail sheet. You can also ask Orion to share a view, and it confirms with you before sharing. Sharing does not take the view away from the project that created it. That project keeps using it. To reference a shared view, open the other project’s Project Settings and select the Views tab:
Project Settings is open on Views, with Referenced and Shared from this project sections. A red outline highlights the Add catalog view button above the referenced views.

Manage view references in Project Settings

  1. Select Add catalog view
  2. Search for the view by name
  3. Select Add on its row
The Add catalog view dialog shows a search field and a matching view with an Add button. A red outline highlights the search and its matching result.

Find a catalog view to add to the project

The view then appears under Referenced, with the time of its last run. A referenced view counts as data for that project. A project with no data source of its own can still analyze one. Shared from this project lists the views this project has put in the catalog, each with the number of projects using it. That count includes this project, so a view nobody else has referenced reads as one project. A referenced view reads the catalog’s result rather than running in your project, so refreshing it happens in the catalog. See Running catalog metrics.

Removing a Referenced View

Open the Views tab and use the remove control on the view’s row under Referenced. The project is disconnected from the catalog view. Nothing is deleted, and other projects referencing the same view keep theirs. Orion refuses the removal while something in this project still reads the view, and names what. Remove or repoint those first, then remove the reference.
Removing a reference removes the view for everyone in the project.

Who Can Use Views

  • Viewers: read a view’s result when project access and any catalog group restrictions allow it. Run, schedule, code, and delete controls are unavailable
  • Analysts: create, run, edit, and share views, and add or remove references on the Views tab
  • Admins: do all of that for any view in the workspace
Analysts adding a reference need access to the target project and every project that already uses the view. Removing one requires access only to the project you remove it from. Tenant admins can manage references across projects.
A viewer holding a Group Analyst or Group Admin seat acts with that higher role in the projects they reach through it.