Skip to main content
Appenda
Sign inDownload

Table history

Review what changed on the table you have open, and undo it. Table history is the right rail beside the grid. It shows the same entries as Version control, filtered to one table.

Toolbar History opens the table history rail. Commits are scoped to the open table only.

Overview

Every meaningful change on a table writes one history entry: a CSV import, an enrichment batch, a new field, a type change, a view rename, and similar jobs. Table history lists those entries newest first without leaving the grid.

The workspace Version control tab shows the same feed across every table. Use table history when you are editing one dataset and want context beside the rows.

Open table history

  1. Open a table.
  2. In the toolbar right cluster, click History (clock icon, left of Run).
  3. The rail opens on the right with entries for this table only.
  4. Click History again or the rail close control to dismiss it.

The status bar can show the current table version short ref when an entry is selected.

What appears in the rail

Each row is one entry. It shows a past-tense title such as "Imported 540 rows from CSV" or "Changed field type of Revenue from Text to Number", the local time, who made the change and from where (Desktop UI, agent, API, or MCP), and a short ref.

Enrichment entries show the provider logo and capability name. Schema adds and deletes use green or red accent strokes on the row.

Bulk work is one entry per approved job, not one entry per row or cell.

Undo and redo

Click Undo in the table toolbar, or press ⌘Z, to undo the latest change on the open table. Redo (⇧⌘Z) puts it back. The shortcuts work when you are not typing in a cell.

Undo never erases history. It adds a new entry, such as Undid "Rows deleted", so you can always see what happened and undo the undo.

Undo an older change

  1. Open table history.
  2. Click the entry you want to reverse.
  3. Click Undo this change.

Appenda reverses only that change. Edits made after it stay. If a later change touched the same cells, Appenda stops and lists them. Choose Restore this version anyway to overwrite them, or cancel to keep the newer values.

Restore a version

Restore this version, under the same entry, puts the whole table back the way it was right after that change. Everything that changed since is reversed, again as one new history entry.

What can be undone

ChangeUndo
CSV import, rows added or deletedYes
Fields added or deletedYes
Change field typeYes, including values that were emptied
Enrichment resultsNo. Run the column again or clear its cells
Any change on a table over 100,000 rowsNo

When Undo is not available for an entry, the buttons are disabled and a short line says why.

Undo restores your table. It does not take back calls already sent to a provider or credits already spent.

Tips

  • After Import, open history to confirm one summary entry for the whole file.
  • Click a table name in the workspace Version control feed to open that table with history already visible.
  • In a cloud workspace, an undo syncs to your teammates like any other edit.

FAQs

Is table history different from Version control?
Same entries, different scope. Table history filters to the open table. The Version control tab shows workspace-wide activity.
Why is my filter change missing from history?
Filter and sort tweaks on the active view are not recorded in version history. They stay on the view.
Why is Undo greyed out on an enrichment entry?
Enrichment results are not kept for undo. Run the column again, or clear its cells, to change them.
Does one cell edit create an entry?
Routine single-cell edits are normal table work. Bulk imports, enrichment batches, and similar jobs write one entry per job.