Is it possible to define the options of a Single-Select Field in one place, and have the definition instantiated/referenced/used in different Types? Example: I want to define a Single-Select Type for choosing a “Role”, such as: Content Writer Web Developer Project Manger SEO Specialist Admin Sal…

It sounds like you would be well-served to create a type for this purpose, and then create many-to-one or many-to-many relations (to simulate single- and multi-select respectively). Depending on which App(s) the referring types are in, you may or may not want these ‘enums’ to live in a dedicated Ap…

[image] Chr1sG: create a type for this purpose, and then create many-to-one or many-to-many relations (to simulate single- and multi-select respectively). OK - but could we maybe get an option to display such fields as a Single- or Multi-Select in the UI? I.e., so they would show up in the r…

If you create a many-to-one relation, it should show up on the right hand side but many-to-many will show as collections (on the left).

Yeah, I have also wanted something like this. I think it’s quite similar to this previous request by Chris himself :grin: [image] Fields applicable to all types Ideas & Features Can we please have the possibility to define fields that are to be available for all entities w…

[image] Chr1sG: If you create a many-to-one relation, it should show up on the right hand side but many-to-many will show as collections (on the left). This only works to emulate a “Single Select”. It doesn’t work for my current need, which is to define a “Multi-Select-like” field for specif…

[image] Oshyan: reference data somewhere from a field, then set the field data type, and the referenced data would be represented differently depending on that. So if it was a Rich Text field, it would just instantiate all the data there in markdown or plain text, I guess. If it were a multi-sel…

[image] Oshyan: I think it’s quite similar to this previous request by Chris himself Actually, my original request was more about laziness(!) in that I thought it would be nice to be able to define a workflow once and make it available for multiple types simultaneously, but I can see why what…

Thanks for thinking along with me guys, and Chris for your inside view. :smiley: I know that all this feedback is going into the hopper and the team has to consider many angles, including what people want, and also what is feasible or works within the current back-end design, etc. It may be unlikely…

Bumping this as its something I am finding myself in need of now. For my use case we as an agency provide a list of Services, it would really help to have this Services list as a global collection that can be used as options in multi-select fields in various databases. Almost thinking of creating …

My two cents From semantic point of view Single and Multi Selects are treated as a part of its parent Database. when you share a Template it will be included when you move Database to another Space it also moves As we know its specifics (e.g. Icon, color, relation to parent, security settings) …

Reusing Single- and Multi-Select options?

Get Help

Dimitri_S May 12, 2022, 12:30pm 12

I agree, but the process of creating “global” single/multi-selects can be made more intuitive and less messy, I also think it would be a relatively easy feature to implement:

Topic		Replies	Views
Global single and multi-select field options Ideas & Features	11	1211	November 18, 2025
Convert select fields into regular databases Ideas & Features flexible-domain	24	142	October 30, 2025
How to create Single-Select and Multi-Select fields via Integration API? Get Help integration	2	484	April 10, 2023
Fields applicable to all types Ideas & Features flexible-domain	13	3458	September 7, 2020
To easily change Single Select Field to Multi Select one Ideas & Features	2	52	August 25, 2025

Reusing Single- and Multi-Select options?

Related topics