# CHANGELOG: April 8 / Convert entities to another Type, Zendesk integration, Schema changes in Audit Log **URL:** https://community.fibery.io/t/changelog-april-8-convert-entities-to-another-type-zendesk-integration-schema-changes-in-audit-log/1542 **Category:** Changelog **Created:** [April 8, 2021, 12:34pm UTC](https://community.fibery.io/t/changelog-april-8-convert-entities-to-another-type-zendesk-integration-schema-changes-in-audit-log/1542 "2021-04-08T12:34:55Z") **Posts on this page:** 1 **Showing post:** 19
### Author: ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp) #### Post date: [October 28, 2021, 8:52pm UTC](https://community.fibery.io/t/changelog-april-8-convert-entities-to-another-type-zendesk-integration-schema-changes-in-audit-log/1542/19 "2021-10-28T20:52:57Z")
Guys, wanted to flag up this issue again, and the very similar conversation over in > [@\[APPROVED\] Replace All References (or convert to type?)](https://community.fibery.io/t/approved-replace-all-references-or-convert-to-type/982/9): > > Just FWIW I have occasionally deleted a view when I have realised that an alternative visualisation would be better, and then gone on to discover that I have unwittingly broken the references to that view elsewhere. Even without automatic reference conversion, it would be nice if all views/documents had a way to show where they were referenced (like is the case for entities) so that I can see what I might be breaking. Also, I think if/when it becomes possible to embed as well as mention a vie… My team is working in some multi-level structures in a software system. Basically, three apps, One has 4 levels, the other 3. As we build it out, we are seeing that stuff we thought was at the very bottom is actually a level up, or even something at the top of one should be down two levels. But once an item is created at one level, then commented on, referenced, and related to, you can’t move it easily to another level without losing all that context. This incidentally is another problem I spoke of here in the above-referenced thread: > [@\[APPROVED\] Replace All References (or convert to type?)](https://community.fibery.io/t/approved-replace-all-references-or-convert-to-type/982/8): > > 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. We are now getting stuck on how to move things to the proper level because some of these entities have months of references, comments, etc. which will all be lost. Manually recreating that stuff is a ton of work, plus you will lose the original time that that content was created, which is very key. It’s important for us to see that a Meeting entity referenced a server solution we are considering 2 months ago. If I delete the server solution because it belongs in another area of my hierarchy, and then go manually recreate the reference, the reference is now from today, and not when it was made originally in the meeting. Thanks for considering and hope to see movement on this soon! --- _[View the full topic](https://community.fibery.io/t/changelog-april-8-convert-entities-to-another-type-zendesk-integration-schema-changes-in-audit-log/1542)._