Hi all, I’m at a stage where it’s no longer legit to make changes directly on the prod env.
What are your best practices for managing changes in the base’s structure and design? (changing field type, editing formulas, editing scripts, adding tables etc.)
For example, is there a way to connect to git and keep track of changes to table schemas (not data sync)?
How do you make changes in a DEV base, and then push them to production? Do you use dedicated branches in git for these changes?
Hm what difficulties did you face using the App Sandbox for this?
https://support.airtable.com/v1/docs/app-sandbox-in-airtable
No tracking of changes, but it does handle the making changes in dev to push to production bit at least?
Hey
Somehow related:
You might want to check out AirDiff: https://airdiff.modernstack.io/product for tracking changes to your data base schema. This tool was built by
I personally did not give it a shot yet, but I will hopefully soon.
Mike, Consultant @ Automatic Nation
YouTube Channel
Thanks for the mention
And yes, AirDiff does all of this on the base/schema tracking side. (https://airdiff.modernstack.io/product)
Essentially you can take a snapshot of your schema in any base in Airtable. Each schema scan is hashed out considering its tables, fields, field configurations (AI Agent descriptions, field names, table names, everything), and then hashed out. Then any future scans are compared against the latest scan, generating a changelog of anything that has changed since then! You’re also able to go back to your history of scans to see what the exact schema was in any of the scans, so you can keep a log of what things were a week ago, month ago, 3 months ago, etc.
The entire schema to markdown or JSON if you want to work with ChatGPT or another LLM on giving context to your Airtable schema as well. Users so far have really enjoyed the features and UX. Definitely check it out, there’s a free plan to get started.
As for best practices, there’s a new feature right now that’s still in ‘Beta’ for Airtable called Sandbox mode that helps with the dev → production push a bit, you can really only have a single ‘sandbox branch’ in this mode, and it completely locks all changes in the production branch when the sandbox is on, so there’s some things you’ll need to be aware of when turning that one.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.