I have found a few posts about this already, but none more recent than two years ago. I find this feature gap baffling, and I can’t imagine being able to use Airtable without it.
My use-case is simple. I have an ever-growing list of sign-in for meetings. I want to have a separate membership table that has one row per unique person - a given person will sign in to many meetings - and, for example, a count of the number of meetings that person has attended. This is trivial to do with linked records and Rollup columns. However, as best as I can tell, for each new record in the source sign-in sheet, I have to manually add those linked records to the derived membership table. That is a nonstarter for me, and I have several other use-cases I was hoping to make after this prototype, but they all require this very simple feature.
I don’t understand why a column can’t be set to automatically link to all records in a corresponding table. This is the most basic feature of any relational system. What am I missing?
One easy way to do the manually linking is that you can just start typing in the linked field, and it will keep narrowing down your potential matches until you hit return to accept one of the matches. If there are no matching records, just hit return and it will automatically create a new linked record based on what you just typed.
I’m with you. I accept form submissions that include an email address. I want to populate a secondary table with these emails as a primary key, but this seems not possible. A linked/replicated column like you suggest would solve my problem AFAICT.
Having to type or copy/paste columns to keep two tables in sync is madness.
While it’s not a fully automated solution, I did write a script for the Scripting Block to deal with a similar issue that at least removes the majority of the pain of manually syncing tables. I’m sure it could be adapted to do what you need with the click of a button: