+2Does anyone know of a way to duplicate a base while keeping the record ids the same?
We are trying to set up a "staging" instance of our Airtable tables but we have references to the record ids outside of Airtable. This causes all of the references break because new records ids are generated when we duplicate the base.
Is there any way around this?
Thanks,
Chris
Best answer by kuovonne
It is not possible to keep record IDs (or any of the ids) the same when duplicating a base. Can you set up your system to reference records by name or some other property?
+29It is not possible to keep record IDs (or any of the ids) the same when duplicating a base. Can you set up your system to reference records by name or some other property?
+2It is not possible to keep record IDs (or any of the ids) the same when duplicating a base. Can you set up your system to reference records by name or some other property?
Thanks for the quick response!
Unfortunately, it would take some re-architecting to reference a different field.
I may look into creating a script that grabs another unique value from the table and uses that to map to the correct record id in the staging table.
I am running into a similar problem. Did you find a workaround? In general setting up a staging environment with airtable seems to be an afterthought. We are going to move to supabase so we have something a bit more robust, but this is a whole process since we'll have to create a front end for all our interfaces.
The only thing that I can think of is storing the id in a text field and then referencing that instead of the airtable record.id. That way you are still referencing the "id" but instead of accessing that through the build in property you are accessing it through a text field named id or uid if you want to distinguish it.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.