I understand it breaking the Many side, as it is now a different type of field, the issue is that it also breaks the One side of the relationship in formulas. I haven’t tested it for rules.
Not sure what you mean by ‘breaks’ the relationship. Do you mean that values are lost?
Or do you mean that places (formulas, automations) that rely on this field get broken.
If the former, then it’s a bug. If the latter, then it’s a side-effect of the fact that, under the hood, a relation conversion is actually a new relation getting created and the existing one getting deleted.
Hi Ron, this is the way it is implemented.
The reason is as this change is destructive and we need to make sure that User has ability to undo this. So original relation is preserved for 90 days and as it is preserved, it occupies the same “field slot“ on the other end and that slot cannot be reused. Also it is much safer to have new fields generated for converted relation so it doesn’t conflict with any saved configurations.
You may see this feature as a helpful shortcut to migrate data between old and new relation.
I understand what you want but it is not easy to implement (e.g. auto update formulas or automations) atm.
1 Like
Hi Viktar,
This makes sense. Thanks for the explanation!
Would be nice to have at some point, but it’s also not the end of the world. Just a bit more configuration.
Thanks!
1 Like