Convert & Delete/Replace Entity preserving references

[B_Sp]

I would like to add a hearty vote for this feature as well. I also took the liberty to edit the title of this with the addition of “preserve references” hopefully that is OK @cannibalflea

My team has been in Fibery a while, since late 2019, and we have a lot of db hierarchy structures that are evolving, and could use some edit. This could be solved by Polymorphic Relations but I know that is some time away. We track a lot of static things, like products, service providers, equipment, etc. and some of the structures of these things need edit after 4 + years - we need another level in our hierarchy for equipment, a sub-product is now a product, or vice versa, etc. This ideally would lead to moving these older entities, with tons of references and history, into new structures. In more free-form tools like Notion or Tana I can just move those out and basically “retag” them into new DB’s with no issue. The entity stays the same and I don’t need to “convert” it to a new Type. There might be some issues with field mapping but there are simple ways those tools solve that.

However right now in Fibery the conversion feature only maintains comments as far as I can tell. very importantly all references will be lost. This means we are sitting with a lot of key entities that are core to our business - like products, etc., that are stuck in the wrong structure and we can’t move them at the risk of losing years of history.

I also wanted to repost here some other suggestions I had for more involved process in converting entities. Again I think with the degree of inflexibility within Fibery because entities are stuck in DB’s, which I would call the more “atomic” level in Fibery, vs. say another tool like Notion where the entity is the more atomic level, and DB’s are formed more loosely to essentially group entities, but the entity (or page, issue, node etc. - however the other apps refer to them) are the core base-level piece of data.

@B_Sp

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.

Thanks!