Sometimes a table just gets a little too big, and something has to be done about it. You have two options:
Simply delete the oldest entries.
Selectively copy items ready to be archived from the original table to another table.
Decisions need to be made
Which rows to copy, and
which columns needs to be copied.
These are questions that completely depends on the context of your document.
This doc contains three examples:
The examples below will move rows from the arcData table to the arcArchive table. (Tables shown below.)
Click on the Delete row button to simply delete a row from the table.
Click on the Move to Arc button to move a row from arcData table to arcArchive, and then to delete the row from the original arcData table. Move to Arc contains two steps in a runaction() formula. The first action copies the row to the arcArchive table, the second action deletes the row from the arcData table (The runaction() formula is necessary to ensure 100% that the two actions are executed in the correct sequence.)
Click on the Archive check box to trigger a row-based automation. This will activate the Auto Move button, and trigger the row-based automation to execute the runactions on the Move to Arc buttons.
(I have used row-based, so that you do not need to wait for the time based trigger to come around when you try out this document. But IRL you would most probably have a different trigger (rows older than a certain duration, for example) with a time-based automation, say once a month.)
Note: For both of the moves the columns Lookup Value and Formula retains their type.
For further info on Automation check out the video from Coda below.