Would like the ability to define the options of a Single-Select or Multi-Select field in one place, and have the definition instantiated/referenced/used in different Types? Example: Defining a Single-Select field for choosing a “Role Type”, such as: Content Writer Web Developer Project Manger SEO…

Hi, Dimitri! I think in your case it will be better to create a specific Database, called Role In fact our Single Select and Multi-Select fields are Databases (1-many; m2m) with a friendly UI for simple cases If that’s not enough - one Database, relations to other Database you want - and you’ll g…

Yeah this works very well, but there are two problem with this approach: 1) Its unintuitive - only seasoned Fibery users know that multi-select fields are secretly hidden mini-databases. Maybe having a normally off checkbox on the single/multi-select field creation modal for something like “Make t…

Also, as was pointed out in the other thread, multi-selects appear in the right hand panel of entity view, whereas a many-to-many relationship (to an enum database) appears as a collection, which is often unnecessary for a simple multi-select functionality.

I just discovered this feature, after 5 months of using Fibery :joy: Thanks, it makes things a lot easier. Some questions though: What I understand is that: A multiselect field is a mini-database that is part of its parent database X. The name of the minidatabase is ‘Database X name, Select field…

Yes You can change the select field name Yes (but improvements to select field config are likely) Yes The default name for the field created in Y is the ‘full name’ of the select (i.e. the owning database name plus the field name) so this indicates that the select is ‘owned’ by another db. Yes […

[image] Chr1sG: All the things that are missing are present if a user creates a database for global re-use instead of re-using a select field, and I’m not sure what you think a ‘lightweight database’ would have that a normal database wouldn’t have…? What I see is that current development in f…

personally, I dont use single and multi select field anymore, if I got some things like that, it’d be better to just create an database for that I’m using a space for all type of single select, or multi select because you dont know which database in the future willing to be used it Also the custom…

Per the suggestion, I’ve gotten in the habit of using databases in many cases instead of single/multi select fields. However, there are a few pain points with this, mostly on the UI front: [image] Chr1sG: multi-selects appear in the right hand panel of entity view, whereas a many-to-many relat…

Now you can duplicate single- or multi-select to another database [image] 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 Changelog This relea…

This is just a direct as-is copy and not a true mirror, correct? i.e., if the original is updated (option added, removed, or changed), the duplicated field’s options won’t be

Global single and multi-select field options

Ideas & Features

mdubakov April 17, 2025, 1:01pm 10

Now you can duplicate single- or multi-select to another database

Topic		Replies	Views
Reusing Single- and Multi-Select options? Get Help	11	1262	May 12, 2022
Convert select fields into regular databases Ideas & Features flexible-domain	24	171	October 30, 2025
How can I create a Muli Select using the API? API & Programming	2	152	April 11, 2024
To easily change Single Select Field to Multi Select one Ideas & Features	2	57	August 25, 2025
Dependent Dropdown Field Type Ideas & Features	27	3894	March 4, 2026

Global single and multi-select field options

Related topics