Baserow buying guide: should task rows follow a project venue rename?
Use two mock tables to verify links and read-only lookups, and separate live references from history that must stay fixed.
A project’s venue changes from Blue Hall to East Hall. Should its task rows show the new name or retain the old one? Both can be right: the field may give current directions or preserve what an earlier notice said. Baserow fits the first case. Its documentation defines Link to table as a relationship between rows. Lookup displays a source value in another table and is not directly editable. The 0.3 release introduced links, and the 1.21 notes already mention Lookup.
Test one project and two tasks
In a fictional model exhibition, project P-01 lists Blue Hall. Task T-01 makes signs and T-02 places models; both link to P-01. Show the same venue Lookup on both and store ordinary text on T-01: “Venue when announced: Blue Hall.” In a possible trial, change the source to East Hall. Both Lookup values should show East Hall; the ordinary text should still say Blue Hall. Editing only that text should not change the project source. These are acceptance criteria, not test results or a recommendation to update all historical tasks.

Original concept, not a product screen or a measured result. Live references and preserved history belong in separate fields.
Before migrating, test three samples with no personal information: one with a clear project code, one with a repeated project name but a different code, and one with no code. Check that links point to the expected source row and that incomplete tasks can await review rather than guessing a project. Treat fields visible in the task interface as a separate check; showing or hiding a column is not proof of security authorization. No real data, sharing links or permission changes are needed.
When not to migrate
For one short table with rarely changing fields, the existing sheet with codes and a lookup formula may suffice. A live Lookup must not replace historical text such as an already sent notice. Compare how many task edits one source change saves with the time needed to fill missing codes, maintain links and check exports. Use the same small synthetic sample for both approaches. Expand only if you can trace the source and keep current values separate from history.
Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.
Original source:baserow.io