Here's a view where I stopped using an Enum column in favor of a Yes/No column:
It looks like an Enum button display with two choices but it's a Yes/No column:
The advantage of using Yes/No is that it's programable. In my app, the words shown on the buttons change when the language of the app changes. But, unlike an Enum, I never get an error due to the word written to the spreadsheet being different from what the Enum expects.
As I understand it, there was a time when the display values of Yes/No columns were not programmable. So, some people who have been around for a while may not be aware that they are now quite flexible. If that's the case, you might want to take another look at the humble Yes/No column. ๐
โ
โ
That's very handy thank you @Kirk_Masden
Please be aware that Yes/No columns with expressions in display value will slow down the search.