# Create a multi-select field whose options equal all item names in a database **URL:** \ **Category:** Get Help\ **Created:** [March 10, 2026, 10:33pm UTC](https://community.fibery.io/t/create-a-multi-select-field-whose-options-equal-all-item-names-in-a-database/10530 "2026-03-10T22:33:08Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![cadsharp](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cadsharp/32/14008_2.png) [@cadsharp](https://community.fibery.io/u/cadsharp)\ **Post date:** [March 10, 2026, 10:33pm UTC](https://community.fibery.io/t/create-a-multi-select-field-whose-options-equal-all-item-names-in-a-database/10530/1 "2026-03-10T22:33:08Z")
I’m creating a Personnel database for my company. Let’s say it has three items: - Bob - Joe - Tom One of the multi-select fields in this database is “Manages”. I want the options to equal all item names in the database. i.e., “Bob”, “Joe”, “Tom”. Thanks. ---
**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:** [March 10, 2026, 11:15pm UTC](https://community.fibery.io/t/create-a-multi-select-field-whose-options-equal-all-item-names-in-a-database/10530/2 "2026-03-10T23:15:50Z")
Hey! Good to see you on here Keith. Best solution here would be to add a “self-relation”: [Fibery](https://the.fibery.io/@public/User_Guide/Guide/Self-relations-328) Same way you can set “Parent Doc” and “Sub Docs”, you can set a set relation for “Managing” and “Managed by”. It’s not exactly what you asked, but I think it solves the root problem you’re going for. Let me know if I understood it wrong though! ---
**Author:** ![cadsharp](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cadsharp/32/14008_2.png) [@cadsharp](https://community.fibery.io/u/cadsharp)\ **Post date:** [March 10, 2026, 11:56pm UTC](https://community.fibery.io/t/create-a-multi-select-field-whose-options-equal-all-item-names-in-a-database/10530/3 "2026-03-10T23:56:00Z")
Hi Ron. Thanks for sharing. Yes, that creates a field that lets be choose users from the owning database, but UI-wise I’d prefer to stick with the multi-select field, so it looks like I’ll be manually adding the multi-select options I need. No worries though. ---
**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:** [March 11, 2026, 7:36am UTC](https://community.fibery.io/t/create-a-multi-select-field-whose-options-equal-all-item-names-in-a-database/10530/4 "2026-03-11T07:36:28Z")
If you like the UI of a multi-select, you can still follow @RonMakesSystems’s advice and create a self-relation, but then choose to display the collection field as one of the upper fields on entity view. If that’s still not good enough, would love to hear what you like about multi-selects that you don’t get with a relation. ---
**Author:** ![cadsharp](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cadsharp/32/14008_2.png) [@cadsharp](https://community.fibery.io/u/cadsharp)\ **Post date:** [March 12, 2026, 4:07am UTC](https://community.fibery.io/t/create-a-multi-select-field-whose-options-equal-all-item-names-in-a-database/10530/5 "2026-03-12T04:07:05Z")
Thank you! Yeah, that’s a great tip. Though I’m not clear on why these self-relations have to create additional fields. I renamed the Personnel duplicates to reference the fields they’re associated with, and then hid them. (They’re not hidden below.) ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/0117e216da2f0b7d8c873c19be95b601ef45ce87.png) ---
**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:** [March 12, 2026, 6:27am UTC](https://community.fibery.io/t/create-a-multi-select-field-whose-options-equal-all-item-names-in-a-database/10530/6 "2026-03-12T06:27:59Z")
You don’t need to create the relationship twice. If you have a single relationship, you can name one field ‘Manages’ and the other ‘Managed By’. If you then look at Bob’s entity view and decide to set Joe as one of the people he manages, when you look at Joe’s entity view, you will see that Bob is already marked as who he is managed by. > **[Self-relations](https://the.fibery.io/@public/User_Guide/Guide/Self-relations-328)**