# \[DONE\] Embed Custom Views into Entity View

**URL:** https://community.fibery.io/t/done-embed-custom-views-into-entity-view/936
**Category:** Ideas & Features
**Tags:** blocks
**Created:** [August 30, 2020, 4:15am UTC](https://community.fibery.io/t/done-embed-custom-views-into-entity-view/936 "2020-08-30T04:15:30Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)
#### Post date: [September 7, 2020, 7:21am UTC](https://community.fibery.io/t/done-embed-custom-views-into-entity-view/936/5 "2020-09-07T07:21:20Z")

</div>

> [@Oshyan](#):
>
> The alternative is to develop an ability to add arbitrary Collections to any Type

This seems to be close to the polymorphism that has been discussed elsewhere, and that seems to me to be a preferable solution. I note that you specifically state

> [@Oshyan](#):
>
> _without_ relations

but wouldn’t using relations provide for

> [@Oshyan](#):
>
> allowing Embeds to take on Context just like Backlinks

I think polymorphism + enhancing relations à la [More Capability to edit/view related entities in Collections - aka Subtables](https://community.fibery.io/t/more-capability-to-edit-view-related-entities-in-connections-aka-subtables/520) is the better way to go.

As an aside, isn’t it the case that ‘embedding views/entities’ is just a way to allow the details of something that can already be #mentioned (view or entity) to become visible at the mentioning level. So you’re basically saving the user having to click-through, right?

---

_[View the full topic](https://community.fibery.io/t/done-embed-custom-views-into-entity-view/936)._