# \[DONE\] Convert select options to database **URL:** \ **Category:** Ideas & Features\ **Tags:** flexible-domain\ **Created:** [November 18, 2025, 2:56am UTC](https://community.fibery.io/t/done-convert-select-options-to-database/10035 "2025-11-18T02:56:19Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![AdVhPkgKad](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\ **Post date:** [November 18, 2025, 2:56am UTC](https://community.fibery.io/t/done-convert-select-options-to-database/10035/1 "2025-11-18T02:56:19Z")
I have a select that I want to duplicate to multiple database locations (perhaps even using the values to link two entities automatically). As since this release, it has been possible to copy the select from one database to another. > [@April 17, 2025 / leaf\_fluttering\_in\_wind Duplicate Field, Improve Entity creation flow when entity name is generated via a formula, Multi-accounts in Google calendar](https://community.fibery.io/t/april-17-2025-duplicate-field-improve-entity-creation-flow-when-entity-name-is-generated-via-a-formula-multi-accounts-in-google-calendar/8625): > > This release has several quality of life improvements for creators and users. Enjoy! leaf_fluttering_in_wind Duplicate Field Imagine you setup a long and beautiful single-select field for Tasks database and suddenly realise that you need it in Bugs database as well. You had to re-create it from scratch… No more! Now you can quickly duplicate basic fields (including single- and multi-selects) into another database. squid Improve Entity creation flow when entity name is generated via a… However, due to the maintenance required to keep these two or more copies of the list synced, it’d likely be better suited stored as its own database. The issue I see is in converting the existing data; what happens to the old field when a new relationship is added? If the name is an exact match, then setting up ‘Automatically link A to B’ shouldn’t be too difficult. I’m not too concerned there (though maintaining the link after deleting the original field would break this, no?) But all of the views that looked at the old select field will require updating—forms and entity views included—and it will also break all reports. Could you perhaps consider the ability to generate a clean new database from a select, link entities up automatically, and re-route the references so it’s a seamless experience? Huge ask, I know. ---
**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\ **Post date:** [November 19, 2025, 3:30pm UTC](https://community.fibery.io/t/done-convert-select-options-to-database/10035/2 "2025-11-19T15:30:21Z")
It’s recommended that we use the AI Assistant for this: [Convert select fields into regular databases - #23 by carson](https://community.fibery.io/t/convert-select-fields-into-regular-databases/6629/23) Although I do believe the request should remain open for voting, as AI credits are limited and this feature is likely needed a lot in the first few months of setting up a workspace ---
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [February 26, 2026, 11:42am UTC](https://community.fibery.io/t/done-convert-select-options-to-database/10035/3 "2026-02-26T11:42:05Z")
I need this now too… While its not hard to create and replicate, it gets very hard when there are dozens of views, rules, etc which depend on that select field… The reason it’s needed is that now the select field needs to part of the templating, and I prefer to template using the same database (name changes change everything), and adding an option is added everywhere, etc. Doing this with selects isn’t ideal. That said, will probably stick to selects for now until this feature is released since refactoring the views and automations has a higher chance of things breaking (for private views and user made views) than the selects. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [August 6, 2026, 2:21pm UTC](https://community.fibery.io/t/done-convert-select-options-to-database/10035/4 "2026-08-06T14:21:52Z")
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) ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [August 20, 2026, 8:46am UTC](https://community.fibery.io/t/done-convert-select-options-to-database/10035/5 "2026-08-20T08:46:50Z")