I agree with this and you are talking about some more advanced ways to relate two Entities that I would really advocate for. There are numerous discussions in the community around aspects of this, sorry I don’t have time to find the references, but off the top of my head:
-
Converting an Entity into an Entity within another Type, with full mapping options, and other options like “maintain references” and “copy comments” and other advanced copying
-
Linking An entity to a newly created entity that would copy over much of the original entity’s data, but be in another Type
-
Your request to merge two related entities into one
-
Full tracking of the history trail of the connection being made between the two Entities: in the new one, info that it originated with the previous one; auto-write to comments about the “conversion” from the originating entity, etc.
I would have great use of this, and I advocate for dev time to be spend to build out sophisticated capability within Fibery to move Entities in various ways between Types, and to merge them if need be. I think this is going to be essential down the road due to the flexibility of Fibery and constant need to tweak set-ups and teams’ needs evolve.