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.

Input columns are currently in beta. Reach out to Omni support to have this feature enabled.
Input columns let you add editable columns directly to a query result. Instead of building a separate table or directly modifying your database, you can annotate rows inline — adding values that attach to specific rows and persist across query refreshes. Input columns are a good fit when you need to layer human judgment or operational context on top of data that already lives in your database. For example:
  • Triage and review workflows — Flag records as reviewed, escalated, or resolved directly in the query result (e.g., a table of support tickets or open orders)
  • Qualitative scoring — Assign priority scores, confidence ratings, or categorical labels to rows (e.g., rating leads by quality after reviewing enriched account data)
  • Collaborative annotation — Let a team of analysts or operators add notes to shared dashboards without needing to touch the database
  • Exception tracking — Mark anomalies or outliers with a reason code as part of a data review process
  • Forecast overrides — Layer human adjustments on top of forecasts (e.g., a sales manager overriding a rep’s pipeline number, or ops adjusting an inventory projection

​
Common questions

Yes. Input columns use the same writeback mechanism as data input tables: values are written as a table in your connection’s scratch schema and joined back to your query results automatically.
When you add an input column to a query, you choose one or more key columns — dimensions from the query that uniquely identify each row, like a customer ID or order number. Omni uses these keys to match your entered values to the right rows, even as the underlying query data changes over time.Note: The column’s Key columns setting can’t be changed after the input column is created.
Yes. When creating the input column, set the Edit mode to Published. End users will then be able to enter values on a live dashboard.
Input columns currently support text and number data types.Note: The column’s Data type setting can’t be changed after the input column is created.

​
Requirements

To use input columns, you’ll need:
  • A scratch schema configured on the connection. Unlike data input tables, input columns require database writebacks to be enabled. Refer to the setup guide for your database for instructions.
  • Restricted Querier, Querier, or Connection Admin permissions
  • To have the Upload data ability enabled. This must be enabled for the organization and, if the document is shared with others, also in the document’s settings.

​
Adding an input column

Input columns are added from within a query result in a workbook or dashboard.
1
Open a query result in a workbook or dashboard.
2
Click the icon in the column header, then select Add input column.
3
In the dialog, configure the input column:
  • Column name — A label for the column. Alphanumeric characters only.
  • Data type — Choose Text or Number.
  • Edit mode — Choose when the column should be editable. Refer to Edit modes for more information.
  • Key columns — Select one or more dimensions to use as the row identifier. Refer to Choosing key columns for more information.
Heads up! Data types and key columns can’t be changed after the column is created. To change them, you’ll need to delete and then re-create the column.
4
Click Create.
The input column will appear in the query result. To enter values, see Editing values.

​
Edit modes

When creating an input column, you choose an edit mode that controls when the column is editable:
ModeEditable inUse case
DraftDraft documentsContent creators annotate data while building
PublishedPublished documentsEnd users fill in values on a live dashboard

​
Choosing key columns

Key columns are the dimensions Omni uses to match your input values to the right rows. When selecting key columns:
  • Choose columns that uniquely identify each row. If the same combination of key values appears more than once, input values will apply to all matching rows.
  • Choose columns with stable values. If a key value changes — for example, a product is renamed — previously entered values won’t match the updated key.
You can select multiple key columns to form a composite key. For example, if product IDs aren’t unique across regions, combining region and product_id may be necessary to uniquely identify rows.

​
Editing values

By default, input columns are locked and will display a in the column header. To edit the column’s values:
1
Click the icon to unlock the column. The cells will become editable.
2
Click a cell and type a value. Press Enter to move to the next row, or Escape to cancel the current edit.
3
When you’re done, click the icon again to lock the column and save your changes.
Unsaved edits are shown as a preview until the column is locked. Values are written to the database’s scratch schema when you re-lock the column.

​
Editing an input column’s configuration

Data types and key columns can’t be changed after the input column is created. To change them, delete the column and then re-create it.
To rename an input column or change its edit mode:
1
Click the icon in the input column’s header.
2
Select Edit column.
3
Update the name or edit mode, then click Save.

​
Deleting an input column

Deleting an input column permanently removes the column and all values entered in it. This action can’t be undone.
1
Click the icon in the input column’s header.
2
Select Delete column.
3
When prompted, confirm the deletion.

​
Current Limitations

  • Input columns are scoped to the workbook and cannot be promoted to the Shared model layer yet