I’m currently evaluating Airtable for broader adoption on my team, and this limitation on top of other limitations with color is really giving me pause and is close to being a deal breaker. Color coding information in consistent ways is vitally important, especially working with art disciplines, and I don’t want to have to have all information in one giant table in order to ensure a consistent single select array of color coded entries, or rely on hacky automations duplicating lots of information & that can become out of sync later if original single select list changes, which in my use case it would because it’s for a list that is constantly added to. Conditional color coding works for some things, but for some use cases you want a color to mean a specific thing, and stay that way wherever it is used, and for large lists that are more than handful of options, conditional color coding is extremely clunky if you want to maintain it across tables.

I don’t understand why a look up connection to a valid single select shouldn’t be usable for color, the color information is right there. This is especially important for things like the timeline view where legibility of information is highly color dependant and assigned record colors fill bars in the chart.

Yeah this one has been annoying me for a while, so I should probably resurrect this thread.  Even if it just looked up the color of the first member of the array--that way you don't have to worry about handling conflicts.  And if the data type changes, or the color is removed from the lookup field?  Just go back to default gray...

I reaaaaally don't want to sit there and make a new rule for the 40 different colors.  But here I go...

Yeh this is infuriating given how much synced bases have been pushed as an amazing feature.