# April 9, 2026 / Embed View and some improvements

**URL:** <https://community.fibery.io/t/april-9-2026-embed-view-and-some-improvements/10724>\
**Category:** Changelog\
**Created:** [April 9, 2026, 1:36pm UTC](https://community.fibery.io/t/april-9-2026-embed-view-and-some-improvements/10724 "2026-04-09T13:36:47Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![Jonathan1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jonathan1/32/10038_2.png) [@Jonathan1](https://community.fibery.io/u/Jonathan1)\
**Post date:** [May 7, 2026, 3:02pm UTC](https://community.fibery.io/t/april-9-2026-embed-view-and-some-improvements/10724/17 "2026-05-07T15:02:20Z")

</div>

> [@B\_Sp](#):
>
> I think there is still some work to be done, such as a menu that would map things like dates (talked a little about here) [Add ‘convert’ option to automations so references, comments and files are kept](https://community.fibery.io/t/add-convert-option-to-automations-so-references-comments-and-files-are-kept/4288) and [preservation of dates](https://community.fibery.io/t/convert-entity-doesnt-bring-across-date-field/10723), in particular creation date - so the converted entity gets as much of the original’s metadata.

I agree with you that a “mapping” tool is needed. When we started with Fibery, we used the Project Management template and then, a year later when we had more knowledge of Fibery, decided to re-build it from scratch taking in account our needs. One of the obstacles the team is facing is the inability to easily convert an entity _(and its sub-entities at the same time)_ into a new structure. If you have a Project with 10 Tasks and 20 Subtasks, you need to convert one by one everything and it takes time.

So, having a manner to map the fields and the ability to convert everything linked to the converted entity would be a big step forward.

---

_[View the full topic](https://community.fibery.io/t/april-9-2026-embed-view-and-some-improvements/10724)._