Input columns

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

How it works

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.

For some connections (Postgres, Snowflake, and Databricks), the warehouse table will keep the same name for the life of the input column — either a name you choose or one JustAsk generates automatically. On other connections, JustAsk generates a new warehouse table each time you save the column.

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. JustAsk uses these keys to match your entered values to the right rows, even as the underlying query data changes over time.

Input columns can be edited by other users in a draft or published document, but not both. This includes in a workbook or dashboard. You can specify an Edit mode when creating the input column, and change it as needed.

Access filters

When a topic has access filters (row-level security), JustAsk automatically enforces that the filtered fields must be included in the input column’s mapping key. This prevents data leakage across users or tenants.

Fields from access filters are pre-selected in the input column dialog and cannot be deselected.

If an access filter field is hidden or unavailable in the topic, input column creation will be blocked until the field is surfaced. Ask your data team to add the field to the topic.

Supported data types

Input columns support the following data types:

Data type	Notes
Text
Number	Only accepts numeric values and decimals (ex: 10000, 3.33)
True/false (boolean)	A value of true, yes, y, or 1 sets the column to true; false, no, n, 0 sets it to false. Values display as literal true or false once saved.

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 table upload (scratch) schema configured on the connection. Unlike data input tables, input columns require database writebacks to be enabled. Your admin must configure this.
• Restricted Querier permissions or higher
• To have the Upload data ability enabled. Your admin must enable this for the organization and, if the document is shared with others, it must also be enabled in the document’s settings.

Adding an input column

Input columns are added from within a query result in a workbook or dashboard.

JustAsk Agent

Describe what you want the input column to do and the JustAsk Agent will create it for you:

Add an input text column named Status, using Customer ID as the key column

The agent only sets up the column’s structure — name, data type, edit mode, and key columns. You’ll still need to enter the values into the column.

JustAsk UI

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, Number, or True/false.

   • 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.

     If the topic has access filters configured, fields from those filters are automatically required in the mapping key. These fields are pre-selected and cannot be deselected.

   • Table name — Optional. For Postgres, Snowflake, and Databricks connections, you can define a name for the input column’s underlying warehouse table. This is the name of the warehouse table, not the input column itself — if left blank, JustAsk generates a name automatically.

     Note

     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:

Mode	Editable in	Use case
Draft	Draft documents	Content creators annotate data while building
Published	Published documents	End users fill in values on a live dashboard

Choosing key columns

Key columns are the dimensions JustAsk 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.
• Access filter fields are automatically included. If the topic has access filters configured, those fields are automatically required in the key and cannot be removed. This ensures input values are scoped to the correct user or tenant.

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

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 Save to save your changes.

Unsaved edits are shown as a preview until the column is saved. Values are written to the database’s scratch schema when you re-save the column.

Note

An input column is editable only when its key column(s) are present in the query. If you reuse the column in a query at a different grain, it becomes read-only in that query.

Editing an input column’s configuration

Note

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

Caution

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.

Limitations

Currently, input columns are scoped to the workbook.