Views are the building blocks of queries in Omni — every dimension and measure in the workbook’s field browser belongs to a view. Each view represents a database table and defines the fields, labels, and metadata available for querying.Documentation Index
Fetch the complete documentation index at: https://docs.omni.co/llms.txt
Use this file to discover all available pages before exploring further.
View basics
How do views work?
How do views work?
Views are auto-generated from tables in your database and represent the data available for querying in Omni.In a view file, you define the fields available for querying along with metadata like labels, descriptions, access grants, UI visibility, and AI context.
How are views and topics different?
How are views and topics different?
A view is a single object in your data model, whereas topics sit on top of the data model and reshape it into business-friendly groupings for easier exploration. Topics can include multiple views, which can be curated ahead of time for self-service.Think of views as the objects that make up topics, and topics as the presentation layer you tailor for quick insights. Topics effectively translate your database model into reusable logic for building dashboards and workbooks.
How do I keep Omni views in sync with my database?
How do I keep Omni views in sync with my database?
When tables, columns, or schemas change in your warehouse, run a schema refresh to update the corresponding view files in Omni. See Schema refreshes for more information.
Can I save a query as a view?
Can I save a query as a view?
Yes. A query view is a workbook query saved as a view. Query views can be built from a point-and-click query or a SQL query — the latter are sometimes called SQL-backed query views.Once saved, query views are queryable like any other view, but they’re stored as
.query.view files with their own parameter set. See Query views and Save queries as views for more information.Can I alias a view?
Can I alias a view?
Yes. Aliasing lets you reference a view by an additional name — useful for handling database table renames or for creating duplicate views needed in join logic. See Aliasing views for details.