Dammit ! Another workaround ! Just took me a few days to code my own Node.js two-way sync AirTable <-> GoogleCalendar, I hope this will be shorter… I’ll read those tomorrow and come back here for you :winking_face:
Heya ! After careful reading and study, I understand the workaround. Smart, tricky, beautifully creative, but unfortunately it requires an alteration of the base, and I can already see down the road a time when I have forgotten all about it and mess things up myself.
My logic here : when the workaround creates more complexity than the initial problem it solves, don’t implement it. I will probably rethink my relationships between tables, or accept this limitation until AirTable releases a straightforward solution. Not migrating from old-school DB management for nothing !
So, still waiting for a cleaner solution which probably won’t come…
I’m thinking about limiting the relations to :
Appointments <— Many-to-One —> Invoices <— Many-to-One —> Client
This would be better for data integrity, but requires lookup fields and limits the flexibility for everyday appointment management.
I agree with this logic! Be sure to email email@example.com and let them know how important this feature is to you. It’s a standard feature of all other database systems, so it’s extremely disappointing that Airtable doesn’t have it.