For the case of
Interviews example, I think the best would be to approach it differently:
- have a single table for all candidates, both in play and rejected, elsewhere in the doc
- have a
Is rejected checkbox column there, and update the
Delete button to set that checkbox instead of deleting the row.
- show people in play and rejected tables as two views of that same table, filtering on
Is rejected.Not() and
Is rejected respectively.
Coda is all about having a single source of truth (single table for the data of the same kind) and using views to display different parts of it.
But if this doesn’t work for you and you specifically want to delete a row in one table and insert it into another table, you can do it with a composite action like
RunActions(AddRow(…), DeleteRows(…)), where you first insert thisRow’s data into another table, then delete this row from this table.
P.S. Pardon if I misunderstood the problem. If you already have linked data in
Delete section, you can still follow @Krunal_Sheth’s approach: make a column
Row URL with formula
thisRow.Url(), then in your button call an action
OpenWindow([lookup of your desired row].Row URL) — this should bring that row into focus.