I'm finally making great progress and haven't been frustrated enough to quit yet, so I think I'm going to be able to make this (along with fillout) to help support my makerspace. I hope to eventually move from the free plan to Teams once I know I have all the major pieces in place.
But once I do, and we're using it, I'm concerned that my future clugey attempts to add functionality might break operations. Is there any concept of development, QA and production versions of a workspace?
Hello Jeff,
Concerning interfaces, you can bring modification to pages and not publish them straight away.
For all other points (database structure, formulas, automations) there is no development version as far as I know. I would be very happy if anyone had another information.
Regards,
Pascal
At the price points you mention, there is no built-in support for a development environment connected to a production environment. I manually create a duplicate base for my dev base and then manually copy the changes back to my production base.
I wrote some more of my thoughts on the topic here in Kuovonne's Guide to Airtable.
Hi, sorry to unearth this topic, but the question came in Google results.
I stumbled upon the same problems after making “big” production bases for my clients. Coming from the dev world, I wanted a simple process to separate the development and production environment.
I created an opensource tool to help with that : https://github.com/Squix/airtable-devops
For now it allows to manage Airtable schemas and generate human-readeable changelogs to help reproduce the change in your production base.
I plan to add more integration to be able to track every structural change.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.