Is it possible to allow us to import from a single/multi select? When setting up a new type to replace a select field (I had originally setup a select field but ran into limitations when grouping and nesting entities) it would be great to use the existing importer to bring in fields on a conditional…

[image] carson: It’s similar to Convert select fields into regular databases , 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 aut…

[image] helloitse: Is it possible to allow us to import from a single/multi select? Import from a select field? From where to where?

Import to a new type the entities from a select field within another type. [image]

[image] Single select field options as level in smart folders it would be useful if we could treat Single Selects as first-class Types. If Select fields could optionally be designated as “global” types, then centrally administered, and included in any DB, that would be ideal.

[image] helloitse: Import to a new type the entities from a select field within another type. It is actually possible to link a select field to another database that the original, but you have to do it by opening a select field option and adding a new relation from there. It’s really not reco…

[image] helloitse: Import to a new type the entities from a select field within another type. If you just want to copy the options from a select field as new entities in a new database, then I suggest making a table view with the select field as groups, collapse the groups, select the option …

The one advantage that simple single/multi select fields have is that for the most users, they just show up as drop-downs which are easy to use and understand. Relations to entities (one-to-many or many-to-many) have a much more sophisticated rendering and can sometimes confuse users, especially the…

[image] cannibalflea: It would be amazing if a “Display as” option was provided whereby you could basically tell fibery to treat/render some relation fields as single/multi select fields. If you click the ellipsis (…) for a relation field, you can choose to display as a compact field

[image] Chr1sG: If you click the ellipsis (…) for a relation field, you can choose to display as a compact field Oh, I had missed that feature! Thanks @Chr1sG I think we are almost there, if you could also just disable the drill-down. I know it doesn’t sound like a big deal, but I’ve had qui…

[image] cannibalflea: if you could also just disable the drill-down. I know it doesn’t sound like a big deal, but I’ve had quite a few users just totally lose where they are because they ended up drilling-down into unrelated entities. Do you mean the arrow to navigate to another entity? I th…

Convert select fields into regular databases

Ideas & Features

Matt_Blais September 11, 2024, 7:47pm 4

If Select fields could optionally be designated as “global” types, then centrally administered, and included in any DB, that would be ideal.

Topic		Replies	Views
Convert select options to database Ideas & Features flexible-domain	2	48	February 26, 2026
Global single and multi-select field options Ideas & Features	11	1228	November 18, 2025
Copying fields between databases Get Help	17	699	April 29, 2025
Fields: One-click convert single select to multi select and vice-versa Ideas & Features flexible-domain	0	33	October 28, 2025
Reusing Single- and Multi-Select options? Get Help	11	1262	May 12, 2022

Convert select fields into regular databases

Related topics