30-day version history
30-day version history is on the paid feature list but has no self-service interface yet. The engine does keep a write log and periodic snapshots, and recovery goes through support. Day to day, exporting a .tdbk regularly is still the protection that works.
Where it stands
30-day version history is listed among the paid capabilities and means rolling the data back to a point within the last 30 days. In the current builds (macOS 0.0.9, Windows 0.0.7) there is no self-service interface for it — there is no rollback button in the settings panel.
The mechanism it needs is already in the engine: the data engine persists through a write log plus periodic snapshots, and those files sit in the data folder. When you need a rollback, contact tabledi@thingworks.com.cn with a .tdbk backup and roughly the point in time, and we will help recover it. When a self-service interface ships it will be announced in the changelog and this page will follow.
What to do in the meantime
- Export a
.tdbkregularly — Desktop settings → Data backup. One after each meaningful piece of work, with the date in the filename. It is the most dependable version history available, and it is free. - Export before a big change. Before rewriting formulas, clearing data or importing over the top, take one.
- A table deleted by mistake. There is no recycle bin. Deleting a table asks for confirmation; after that only a backup brings it back.
- A cell edited by mistake. There is no undo. Get into the habit of keeping the raw column and deriving a clean one — then the original data is never overwritten by a formula.
Don't restore snapshots from the data folder by hand
The logs and snapshot files in the data folder are the engine's internal format, and swapping them by hand very easily leaves things inconsistent. Recover through a .tdbk import, or through support.