Yes, I’d love to see this implemented in Airtable as well. Currently, all “value lists” (i.e. single select lists or multiple select lists) are inextricably tied to the field itself. That also means that if you need the same value list tied to another field, you’ll need to manage the 2 value lists independently of one another.
Ultimately, the ideal long-term solution would be for Airtable to separate “value lists” from the fields themselves by making “value lists” their own independently-managed entity — and then different fields could pull from and/or feed into these value lists.
But I don’t think that we will see this behavior change anytime soon in Airtable. It would likely require an entire re-engineering of the entire platform to make this sort of a change. Airtable’s value list behavior is actually identical to how FileMaker’s value lists operated for the first 19 years of that product’s existence. It wasn’t until 19 years later that FileMaker was finally able to separate “value lists” from “fields” — by completely rewriting their entire app from scratch from the ground up. So it was a huge technical change under-the-hood.
