Ok, I think I understand now.
You’re right, that can’t be done using
However, it can be done using a
Lookup table, as you mentioned. See the example below comprised of tables
Table 3. I believe this meets all of your requirements, except for the fact that it uses controlled relational objects from a Lookup table rather than uncontrolled strings from a Select list.
You obviously have specific reasons for using
Select list instead of a
Lookup table, so you may be out of luck here.
For others who might read this in the future, I will share that I LITERALLY NEVER USE
Select list, EVER, not even for throw away purposes – it promotes the injection of de-normalized data into the app, which is a big no-no for data management.
Select list is basically a carry over from spreadsheets, which used them as a way to mimic Lookup tables, precisely because spreadsheets are not relational. But Coda is relational, so why ever use
Select list at all? Using
Select list in Coda largely defeats the point of using Coda.
In fact, I often think they should remove
Select list from the app entirely because it creates more problems than it solves, and it confuses (especially for new users) one of the foundational concepts of the app, which is relational data. There is nothing that can be done with
Select list that cannot be done with a
Lookup table, but there are many things that can be done with Lookup tables that can’t be done with Select lists.
Here’s that example (