# Change "many" to "one" in relation \[DONE\] **URL:** \ **Category:** Get Help\ **Created:** [March 17, 2023, 4:04pm UTC](https://community.fibery.io/t/change-many-to-one-in-relation-done/4145 "2023-03-17T16:04:03Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Michel\_Daviot](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michel_daviot/32/6094_2.png) [@Michel\_Daviot](https://community.fibery.io/u/Michel_Daviot)\ **Post date:** [March 17, 2023, 4:04pm UTC](https://community.fibery.io/t/change-many-to-one-in-relation-done/4145/1 "2023-03-17T16:04:03Z")
Hi, I’ve seen that from one to many it is supported ([CHANGELOG: Apr 27 / My Space (official), Convert to-one relation field → to-many relation field](https://community.fibery.io/t/changelog-apr-27-my-space-official-convert-to-one-relation-field-to-many-relation-field/2745#convert-field-to-one-relation-to-many-relation-2)) What would be the way to change from “many” to “one” ? I have setup by mistake a few weeks ago a relation from Solution “Big Solution” to itself (Versions), and I’d like to change so that a Version has only one “Big Solution”. The field direction is locked : ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/c/cbd02309a9d4713161a8587909dea658d7d60c09.png) Is there any workaround ? ---
**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 17, 2023, 6:20pm UTC](https://community.fibery.io/t/change-many-to-one-in-relation-done/4145/2 "2023-03-17T18:20:27Z")
There’s no way to change an existing relation in that direction, but you can create a new relation and copy paste from table view I suppose. Or you can write an automation that copies over the entities. ---
**Author:** ![Michel\_Daviot](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michel_daviot/32/6094_2.png) [@Michel\_Daviot](https://community.fibery.io/u/Michel_Daviot)\ **Post date:** [March 20, 2023, 11:01am UTC](https://community.fibery.io/t/change-many-to-one-in-relation-done/4145/3 "2023-03-20T11:01:57Z")
Thanks ! I succeeded with copy-paste from table view but afterwards I had several formulas and automations to update by hand. This would be helpful if allowed directly when editing the Entity Field, like changing from one to many. ---
**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 20, 2023, 12:06pm UTC](https://community.fibery.io/t/change-many-to-one-in-relation-done/4145/4 "2023-03-20T12:06:30Z")
Allowing changing from to-many to to-one is much more challenging than the other way, because it is not possible for Fibery to deduce which of the ‘many’ should become the ‘one’. There’s some gnarly UX/UI issues at play, especially if you wanted to convert m:m to 1:1 ---
**Author:** ![Michel\_Daviot](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michel_daviot/32/6094_2.png) [@Michel\_Daviot](https://community.fibery.io/u/Michel_Daviot)\ **Post date:** [March 20, 2023, 3:01pm UTC](https://community.fibery.io/t/change-many-to-one-in-relation-done/4145/5 "2023-03-20T15:01:36Z")
What I would suggest here is only to allow this change to to-one if there is only one value in each entity. So for the end user like me the process would be simply - check and update the table so that each value is single - update the relationship from to-many to to-one And I only suggest going from m:n to m:1, I don’t have a use case for going to 1:1 (it could be done maybe in a second step) ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 3, 2024, 11:58am UTC](https://community.fibery.io/t/change-many-to-one-in-relation-done/4145/6 "2024-10-03T11:58:26Z")
Released today > [@October 3, 2024 / maple\_leaf Quick filters on relation and embedded views, Clean email body, Automations Script AI Assistant, and more](https://community.fibery.io/t/october-3-2024-quick-filters-on-relation-and-embedded-views-clean-email-body-automations-script-ai-assistant-and-more/7492): > > In today’s release we added several improvements to recently released features and made a first step to AI Automations assistant. This is the recent feedback we’ve got from one our customer and it generated a lot of dopamine for our team, just want to share it with you as well. I’m deeply impressed by the technical design of Fibery — you guys seem to make excellent trade-offs and design decisions, preferring to add more powerful & simple higher-level abstractions, rather than special-case feat… ---
**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:** [October 3, 2024, 12:04pm UTC](https://community.fibery.io/t/change-many-to-one-in-relation-done/4145/7 "2024-10-03T12:04:55Z")