# Replace current Entity Views with New Relation Collection Field **URL:** \ **Category:** Ideas & Features\ **Created:** [May 5, 2025, 11:22am UTC](https://community.fibery.io/t/replace-current-entity-views-with-new-relation-collection-field/8726 "2025-05-05T11:22:39Z")\ **Posts on this page:** 1\ **Showing post:** 7
**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:** [May 6, 2025, 8:51am UTC](https://community.fibery.io/t/replace-current-entity-views-with-new-relation-collection-field/8726/7 "2025-05-06T08:51:56Z")
> [@Yuri\_BC](#): > > I suggest that a bigger feature like this needs to have a parent topic There was a [load of discussion about entity view](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995) over many months, that was fed into the decision-making that led to the current entity view design. There may not be much appetite to re-open these topics 🤷 > [@Yuri\_BC](#): > > gives better structured overview of the efforts. Has the team considered such better structure and usage of the Discourse forum? This is the Fibery **community**. Anyone is welcome to contribute - the structure and usage is largely determined by the community members who contribute (i.e. you and others) 🙂 > [@Yuri\_BC](#): > > In what way could AI be leveraged to create a more effective support of and processing of user input for Fibery features? We use AI heavily in managing feature development, including processing feedback (from this community, and from other sources). * * * But I can say, we are not currently focussing on significant changes/improvements to entity view, but it’s possible that there might be some tweaks that will make life easier. --- _[View the full topic](https://community.fibery.io/t/replace-current-entity-views-with-new-relation-collection-field/8726)._