# Stop treating "to-one" relation fields like a red-headed stepchild! **URL:** \ **Category:** Ideas & Features\ **Created:** [May 6, 2025, 10:32pm UTC](https://community.fibery.io/t/stop-treating-to-one-relation-fields-like-a-red-headed-stepchild/8739 "2025-05-06T22:32:57Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [May 7, 2025, 7:52am UTC](https://community.fibery.io/t/stop-treating-to-one-relation-fields-like-a-red-headed-stepchild/8739/2 "2025-05-07T07:52:00Z")
> [@interr0bangr](#): > > The ability to make a relation field required only works on a “to-many” relationship fields In fact, it is the opposite - any to-one relation field can be made required, but to-many relation fields cannot. > [@interr0bangr](#): > > Dynamic values in relation filters only works with “to-many” related entities. Not sure which side of the relation filter you are referring to, but in general a dynamic relation filter can take either of these forms: `To-one field ... is ... This entity → Field value` or `Collection field ... contains ... This entity → Field value` But the right hand side field value needs to be a single entity (a to-one relation). You can vote [here](https://community.fibery.io/t/dynamic-relation-filters-for-to-many-relation/8665) for the option to support `To-one field ... is any of ... This entity → Collection field` > [@interr0bangr](#): > > On whiteboards, only “to-many” relationship lines are displayed At the risk of being pedantic, there is no such thing as a ‘to-many relationship’. The whiteboard can show relations which are m:m, 1:m or m:1 but it is indeed not currently possible to show 1:1 relations. --- _[View the full topic](https://community.fibery.io/t/stop-treating-to-one-relation-fields-like-a-red-headed-stepchild/8739)._