Skip to main content

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.

Query views are views created from an underlying workbook query. This workflow allows you to do light transformations on data, which are then compiled as CTEs when queried.

​
Query view basics

A database view is auto-generated from tables in your database.A query view is a reusable view created from a workbook query. The query can be created using Omni’s point-and-click UI or through SQL.
Users with Connection Admin, Modeler, or Querier permissions can create query views.
Users with Connection Admin, Modeler, or Querier permissions can use query views in workbook queries.
Yes. Query views are included in the Schemas section of the model IDE’s Files browser.You can identify a query view by its file name. Query view file names are appended with .query.view, for example user_facts.query.view.
You can tell the difference between a point-and-click and a SQL query view by how the underlying query is defined in the query view’s file:
  • Point-and-click queries use the query parameter
  • SQL queries use the sql parameter
query:
  fields:
    users.id: id
    users.age: age
    users.created_at: created_at
  base_view: users
  sorts:
    - field: users.created_at
Yes. When you initially create a query view, it will only be available in the workbook where you create it. You’ll need to promote it to the shared model to make it accessible outside the workbook.

​
Creating query views

See Saving queries as views.

​
Editing query views

Query views can be edited in a workbook or in the model IDE. See Editing query views for more information.

​
Next steps