# April 4, 2024 / One-column Entity View layout, mirrored context Folders

**URL:** <https://community.fibery.io/t/april-4-2024-one-column-entity-view-layout-mirrored-context-folders/6054>\
**Category:** Changelog\
**Created:** [April 4, 2024, 12:02pm UTC](https://community.fibery.io/t/april-4-2024-one-column-entity-view-layout-mirrored-context-folders/6054 "2024-04-04T12:02:18Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Post date:** [April 4, 2024, 3:46pm UTC](https://community.fibery.io/t/april-4-2024-one-column-entity-view-layout-mirrored-context-folders/6054/14 "2024-04-04T15:46:20Z")

</div>

> [@ccollins](#):
>
> single fields could be in multiple columns in the main column

| - - - - - to-many view - - - - - -|  
| - button- | -button- | -button- |  
| - - - - - to-many view - - - - - -|  
| - single field - | - single field - |  
| - - - - - to-many view - - - - - -|

This is the need Nr. 1 that I/we have indeed. The separation of single and collection fields has too many drawbacks, actually I don’t see any benefit it at all.

Basically, what is most useful is custom entity view layouts in which fields can be drag dropped in any location the use likes, regardless of the field type.

---

_[View the full topic](https://community.fibery.io/t/april-4-2024-one-column-entity-view-layout-mirrored-context-folders/6054)._