Hi there,
I have a customer who has developed his logistics management system. It has a well done system with interfaces and automations. He wants me to develop new functionalities, interfaces and automations, but I don’t want to touch the system that is in production.
What is the best way to do, clone the complete database, only the table and the affected interface. What about the automations?
Please your comments on the best way to do it.
Thank you,
Joseph
For interfaces, you can create/duplicate/edit interface pages, but leave them in an unpublished state while you’re still testing your changes.
That gives you the opportunity to play around with your changes before rolling them out to other users by publishing the interfaces.
Similar thing with automations. You can test your automation changes before “publishing” the automation changes by clicking on the “Update” button.
However, you’ll still be playing around with the live, actual data in your base.
To avoid that, your only option would be to duplicate your base as a “testing base” and make your changes there.
But note that there would be no quick way to bring back your changes from the “testing base” to the “original base”, since you can’t transfer automations or interfaces between bases.
—ScottWorld, Expert Airtable Consultant
Thanks @ScottWorld.
If I duplicate the whole base, what happens to the automations, should I re-map everything? should I duplicate the automations too?
When you duplicate a base, everything comes along with it. Your records, your automations, your interfaces, everything.
(Although it does give you the option to NOT duplicate your records and record comments.)