

- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Two of the major limitations of Airtable when creating a link from one table (โTable Aโ) to another table (โTable Bโ) is that:
We can ONLY link to the primary field in the other table (โTable Bโ). To truly unleash massive amounts of power & flexibility & customizability in any database system, we need the ability to MANUALLY CHOOSE which field in โTable Aโ should be linked to which field in โTable Bโ.
Linking is always done MANUALLY instead of AUTOMATICALLY. Unlike other database systems, Airtable doesnโt automatically scan for matching values in linked fields โ a human must manually intervene by manually linking records.
Obviously, these changes would graduate Airtable from the realm of โbeginner-level database programโ into a more โadvanced-level database programโ, but it would enable us to create all sorts of advanced database solutions that we canโt create now. It would also remove lots of migration headaches when importing/migrating data into Airtable from other advanced database apps.