This message was deleted.

Good question! I think from my read of their docs you should be able to sync back updates from a target base to the source base, but not create new records there. From our end, there's nothing we'd need to enable - we'd just make the request of the base to update it, and Airtable will let us do it or not.

Thanks @sticky-area-45739 - I just get an error in Stacker if I try to save an updated record that's stored in the sync'd version of the table...

Hm, I'd say it's worth reaching out to support for this one. From looking at the Airtable community it seems like some people are having issues with it just using Airtable. We can try and diagnose via support!

I’d like to see two way sync between a Stacker table (as the source) and Airtable. This would mean new records are only able to be created in the Stacker base and interface but I’d still have a way to show and access this same data on the Airtable side of things. Right now I can’t do that at all.

Interesting, what's your use case there @loud-magazine-63930?

I’m trying to eliminate base tables from Airtable when and where I can so as to not be dependent on Airtable synchronization or up time. Those tables that then get created in Stacker mostly contain static data that end-users never need to update or modify. These Stacker tables are only maintained by Admins but form the basis for tagging other record relationships so I do need to build related record links in Stacker too in order to connect between Airtable data sources and Stacker table sources. It may seem counterintuitive at first, but it would also be useful to then be able to sync those same Stacker base tables back to Airtable for the few instances where a limited number of Airtable users might want to modify and update records either directly or via Airtable interfaces. Without a synced table, I can’t refresh record relationships properly from Airtable, even though those Airtable users would never have a need to be creating new source records. To be more specific about the use case, I have a “species” table in Stacker that contains a list of all species important to a pest identification record. The pest identification table in Airtable is a data source in Stacker and from within the Stacker interface, users that create new ID records can link those IDs back to the related species records via the Stacker defined relationship. For end users this works fine and handles most data entry needs. However, if I want to offer Airtable users similar functionality, I don’t have a read-only, synced Stacker table to reference in Airtable so I can’t build out a similar interface over there. Make sense?

Yes, I think that make sense. I'll feed that back to the team, appreciate you taking the time to explain!