Thanks Scott!
So I was actually looking to auto-update another Table in the second Base, rather than loop back up to the first Base. However! It looks like a workaround might be to have a second copy of each field (so, Status is synced and Status 2 is updated automatically to match Status) and then copy then to the new Table. It didn’t seem to like me copying over the synced value to a new table but it doesn’t mind copying it to a new field in the same table.
Update: and now I seem to have been able to get it to work without that extra field. Only thing I did different was include the update in the same step as find records.
Yes, that’s a clever trick that I didn’t think about — natively syncing in a circle:
- Table A in Base 1 syncs to Table B in Base 2.
- In Base 2: Airtable’s native automations can communicate natively between Table B in Base 2 and Table C in Base 2.
- Then, Table C in Base 2 syncs to Table D in Base 1.
- In Base 1: Table D in Base 1 can be natively automated with Airtable’s Automations to communicate with Table A in Base 1.
Of course, you’ll end up with 4 tables (A, B, C, D) instead of 2 tables (A & B), but it works! :)
Although my favorite way of doing this is still what I think is the easiest way:
Creating a form that updates records in the source base by using Fillout’s advanced forms for Airtable, which lets you update records with a form.
Fillout gives you an Airtable formula that generates a unique link for each record in your source base, which is based on the Record ID of the source record.
So as long as you bring in the record ID of the source record into your destination base, you can generate the URL formula for the source record in the destination base.
I think this is the easiest, cleanest, quickest, and most user-friendly way to handle this! :)
Hope this helps!
If you’d like to hire the best Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld