Skip to main content
Computed columns fill in cells through runs: background work that produces results and spends credits. This page covers how to control when runs happen, where to watch and stop them, and how to look at your table from a different angle without touching the underlying data.

​
Auto-run or run columns yourself

Turn on Auto-run in the toolbar and a column recomputes by itself whenever its inputs change or rows arrive. Its own description says exactly that: it runs cells by themselves when their inputs change or rows arrive. With Auto-run on, decide what happens to cells that already have an answer. Turn on Keep existing results and only errored, empty, or new cells run again, so a run never re-spends credits on a cell that already succeeded. With Auto-run off, a column only computes when you ask it to. Open a column’s header menu and select Run column to see your options, including:
  • Run first 10 rows, a quick check before committing to the whole table
  • Run empty or out-of-date rows, to fill in what is missing
  • Retry failed rows, to try again on cells that errored
  • Force run all rows, which recomputes even cells that already hold answers
  • Choose rows to run…, to pick specific rows
You can also tick rows in the grid and open the Actions menu: an entry there runs every enrichment column across just the rows you selected, and shows the credits that will cost.
Auto-run and Keep existing results only mean something read together. Auto-run decides whether a run starts by itself; Keep existing results decides whether it overwrites answers you already paid for.

​
Watch and stop runs

The counter next to Auto-run shows how many cells the table’s active runs still owe. Open it to see Scheduled column runs, each with its progress and a Cancel button, and Recurring refreshes, the columns set to run again on a standing schedule. While anything is active, Stop all runs halts every run on the table at once. The toolbar also carries a standalone Stop button. It is disabled until something is running, so it teaches you where the brake is before you ever need it. Cells already computing finish; the rest are skipped.

​
Run conditions

Not every row needs a column to run. Open a column’s editor, expand Run conditions, and turn on Only run some rows to build a condition, such as running only where Employees is greater than 50 and Country is US. Add up to eight conditions joined by and or or, or describe what you want and select Generate to have Oneprofile write the condition for you.
Rows that don’t match a run condition are cleared and marked Skipped rather than left holding a stale answer.

​
Views

The view switcher sits in the toolbar next to the run controls. Default view is the table as everyone shares it: no sort, no filters, the shared column visibility. Oneprofile also ships four built-in views:
  • All rows: every row and column, with no filters applied
  • Errored rows: rows where a cell failed to compute
  • Fully computed rows: rows where nothing failed
  • Non-formula columns: hide every computed column
You can also save your own combinations of sort, filters, and visible columns as a named view for everyone on the table to switch to.
1

Set up the table the way you want it

Adjust the sort, add filters, or hide the columns you don’t need.
2

Open the view switcher and select Save current as view…

Name it. It now appears in the view list for anyone with access to the table.
A saved view can be renamed, given a description, duplicated, reordered, or deleted from its own menu. From the same switcher you can select Show as chart to plot the current view instead of listing it. Alongside views, the toolbar carries the tools that shape what you’re looking at right now. Filter narrows rows to ones matching a condition, Sort orders them by one or more columns, and search, labeled Search this table, jumps to matching cells. None of these change your underlying data, so it’s safe to experiment. Save a combination as a view when you want to come back to it later.

​
Next steps