# \[DONE\] Convert select fields into regular databases
**URL:** https://community.fibery.io/t/done-convert-select-fields-into-regular-databases/6629
**Category:** Ideas & Features
**Tags:** flexible-domain
**Created:** [September 11, 2024, 5:06pm UTC](https://community.fibery.io/t/done-convert-select-fields-into-regular-databases/6629 "2024-09-11T17:06:03Z")
**Posts on this page:** 6
**Page:** 2
### Author:  [@cannibalflea](https://community.fibery.io/u/cannibalflea)
#### Post date: [September 14, 2024, 10:43pm UTC](https://community.fibery.io/t/done-convert-select-fields-into-regular-databases/6629/21 "2024-09-14T22:43:59Z")
> [@Chr1sG](#):
>
> Do you think that the usefulness of showing/hiding the arrow is something that varies from relation field to relation field, or is it a property of the database being pointed to?
>
> Is hiding the arrow likely to be useful for every field that is a pointer to this database, or might it be useful to show the arrow for some entity views that have a Status relation field?
>
> My intuition is that the use case is to make a database behave like an enum, not a use case to make specific fields behave like select fields.
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.
---
### Author:  [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)
#### Post date: [September 14, 2024, 10:52pm UTC](https://community.fibery.io/t/done-convert-select-fields-into-regular-databases/6629/22 "2024-09-14T22:52:44Z")
> [@cannibalflea](#):
>
> So I think having an option to make certain databases behave like enums would be quite valuable.
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 😂
---
### Author:  [@carson](https://community.fibery.io/u/carson)
#### Post date: [October 18, 2024, 1:08am UTC](https://community.fibery.io/t/done-convert-select-fields-into-regular-databases/6629/23 "2024-10-18T01:08:19Z")
I’m surprised this isn’t already requested. It’s similar to [Convert select fields into regular databases](https://community.fibery.io/t/convert-select-fields-into-regular-databases/6629), but not the same.
I would love to be able to promote an existing single- or multi-select field to its own database within a space. I often find myself creating a space schema (all the different databases in a space), using a single select field, then later, wishing I could turn it into its own database to be related between other existing databases. The current workaround is to create a new database/type, then copy and paste the names and existing selections from the existing database, and re-create the relation. Since the select fields are secretly just databases, I figure this might not be that difficult to add.
---
### Author:  [@Chr1sG](https://community.fibery.io/u/Chr1sG)
#### Post date: [October 28, 2025, 10:26am UTC](https://community.fibery.io/t/done-convert-select-fields-into-regular-databases/6629/24 "2025-10-28T10:26:09Z")
> [@carson](#):
>
> It’s similar to [Convert select fields into regular databases](https://community.fibery.io/t/convert-select-fields-into-regular-databases/6629), but not the same.
I have merged the topics, because I can’t see any difference in the solution needed.
However, I will add a note here that the AI build agent is now very good at doing such a conversion for you automatically, so I would recommend this route.
---
### Author:  [@Chr1sG](https://community.fibery.io/u/Chr1sG)
#### Post date: [October 30, 2025, 2:12pm UTC](https://community.fibery.io/t/done-convert-select-fields-into-regular-databases/6629/25 "2025-10-30T14:12:10Z")
---
### Author:  [@mdubakov](https://community.fibery.io/u/mdubakov)
#### Post date: [August 6, 2026, 2:23pm UTC](https://community.fibery.io/t/done-convert-select-fields-into-regular-databases/6629/26 "2026-08-06T14:23:21Z")
now you can convert select fields to database [August 6, 2026 / Custom Apps improvements, Convert Select field to Database, Update small part of rich text and add comments via MCP](https://community.fibery.io/t/august-6-2026-custom-apps-improvements-convert-select-field-to-database-update-small-part-of-rich-text-and-add-comments-via-mcp/11145)
[Previous page](https://community.fibery.io/t/done-convert-select-fields-into-regular-databases/6629.md?page=1)