Most of the cases where this has been an issue were related to us trying to use databases as enums with the added benefit of filtering and having a singular source of domain values to manage. So I think having an option to make certain databases behave like enums would be quite valuable. It would be great if these also appear differently from normal databases in the space setup page.
However, there are a few cases where it actually might help to be able to disable fibery’s default drill-down capabilities to avoid confusion. This is especially helpful for team members who might not be spending a lot of time in fibery and just use a few views.
I actually think that the “Display As” feature that was added is yet another great idea that would allow fibery to be both more powerful and easier to use. I have been collecting a bunch of ideas on this which I will post in a new thread. Really appreciate you considering this.
My ideal would be to have this as an option for relation fields that link to an “enum DB”, not for the DB itself, or “Treat this relation like a Single/Multi-Select field” - it would just tweak the relation’s UI to make it look/act like a Select.
But one of the super-useful aspects of “real” Select fields is the colors (and things like “Not Started/Started/Finished” status), so there would need to be a way to assign a color to every entity. Maybe with a formula