Help

The Community will be undergoing maintenance from Friday February 21 - Friday, February 28 and will be "read only" during this time. To learn more, check out our Announcements blog post.

Re: Cutting and Pasting Records between Tables

Solved
Jump to Solution
205 3
cancel
Showing results for 
Search instead for 
Did you mean: 
neildkane
6 - Interface Innovator
6 - Interface Innovator

Is there a foolproof way to do this? I use CTRL-X and CTRL-V, but sometimes it works and sometimes it doesn't...and it may depend on whether the columns and views are arranged the same way between the source and target tables. 

1 Solution

Accepted Solutions
TheTimeSavingCo
18 - Pluto
18 - Pluto

I usually set up views specifically for this where the columns are arranged the same like you mentioned.  You could try to make an automation to do this for you, but it probably isn't worth the effort as the view thing works fine, really

I'm curious as to what your workflow is too; is it that you need to keep the original data static as a form of revision control or something?

See Solution in Thread

4 Replies 4
TheTimeSavingCo
18 - Pluto
18 - Pluto

I usually set up views specifically for this where the columns are arranged the same like you mentioned.  You could try to make an automation to do this for you, but it probably isn't worth the effort as the view thing works fine, really

I'm curious as to what your workflow is too; is it that you need to keep the original data static as a form of revision control or something?

Thanks. Setting up Views will clearly work, and I'm going to revert to that because the cutting and pasting seems extremely error prone. 

TL:DR
I use Airtable (in this case) as a CRM system and I track opportunities by academic year. Once a new academic year rolls around, I want to archive last year's opportunities. Essentially each year we start with a blank slate and create a new record in the table. So what I had wanted to do was create a new table that had all of the old opportunities. That way they could be there for reference purposes, but we don't need them cluttering up the table of current opportunities. 

Ah I see!  Hmm, if it's archiving, what if you duplicated the table instead?  Then your historical data could still be referenced via linked fields if needed, and you could just clear out whatever fields that're outdated in your old table?

Or if you don't need to reference them at all you could just duplicate the entire base too

Thanks. That won't actually work for us since I'm archiving a few records at a time... Since the cutting and pasting of records is so dodgy, I think I'll just revert to filtering to accomplish the same thing.