# \[DONE\] Multiple Entity Views - automated selection 😀 **URL:** \ **Category:** Ideas & Features\ **Tags:** entity-view\ **Created:** [October 13, 2024, 11:04pm UTC](https://community.fibery.io/t/done-multiple-entity-views-automated-selection/7554 "2024-10-13T23:04:27Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [October 13, 2024, 11:04pm UTC](https://community.fibery.io/t/done-multiple-entity-views-automated-selection/7554/1 "2024-10-13T23:04:27Z")
Now that we have multiple entity Views, we are close to being able to “simulate” polymorphic or variadic Types/DBs by automatically hiding fields that are irrelevant to an entity’s “subtype”. The missing piece is a way to designate the _default entity view_ for each entity. **As a first step in this direction, it would be quite helpful if Fibery would simply remember the last entity View selected for each entity, and use that same View _for that entity_** until a different View is manually associated with the entity. Ultimately it will be most useful to designate a single-select or formula field to determine the default entity View for each entity. This will allow for programmatic control which will be important to realize the full potential here. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 14, 2024, 7:09am UTC](https://community.fibery.io/t/done-multiple-entity-views-automated-selection/7554/2 "2024-10-14T07:09:28Z")
> [@Matt\_Blais](#): > > **As a first step in this direction, it would be quite helpful if Fibery would simply remember the last entity View selected for each entity, and use that same View _for that entity_** until a different View is manually associated with the entity. This already works as you described. Last selected view will be shown for a user ---
**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:** [October 14, 2024, 9:08am UTC](https://community.fibery.io/t/done-multiple-entity-views-automated-selection/7554/3 "2024-10-14T09:08:14Z")
> [@Matt\_Blais](#): > > **remember the last entity View selected for each entity, and use that same View _for that entity_** I suspect @Matt_Blais means that when an entity view is chosen for one entity it does not affect the entity view chosen for other entities of the same type. ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [October 14, 2024, 3:32pm UTC](https://community.fibery.io/t/done-multiple-entity-views-automated-selection/7554/4 "2024-10-14T15:32:31Z")
Correct - I did mean that **each entity** should retain its own last-chosen view (for all users). Perhaps this could be an option per DB? ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 15, 2024, 8:18am UTC](https://community.fibery.io/t/done-multiple-entity-views-automated-selection/7554/5 "2024-10-15T08:18:22Z")
> [@Matt\_Blais](#): > > Correct - I did mean that **each entity** should retain its own last-chosen view (for all users). Oh, got it. We will not go for it, but we do want to go for field → default entity view in future ---
**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\ **Post date:** [October 16, 2024, 2:00pm UTC](https://community.fibery.io/t/done-multiple-entity-views-automated-selection/7554/6 "2024-10-16T14:00:04Z")
Great, I had brought this up before as well. To me, if a view is marked as “default” it should load that view for all users, at all times, regardless of what they had previously been looking at. Even better if that view can be dynamically set based on an “entity type” field. Otherwise, when someone gets linked to a certain entity, there’s no way to know they’re looking at the same thing we want them to. [Being able to link directly to a specific view would also help solve this issue for us.](https://community.fibery.io/t/allow-saved-pinned-filters-to-be-applied-via-urls/7488/) ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [October 16, 2024, 3:49pm UTC](https://community.fibery.io/t/done-multiple-entity-views-automated-selection/7554/7 "2024-10-16T15:49:12Z")
> [@mdubakov](#): > > field → default entity view This will suffice if Automations can set the view-controlling field. ---
**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:** [December 7, 2024, 9:31am UTC](https://community.fibery.io/t/done-multiple-entity-views-automated-selection/7554/8 "2024-12-07T09:31:12Z")
I have an issue that: - for nested entities of database Page, - when using two panels side by side, - and I have the Child Pages field entity view tab A - and I have the Description field in entity view tab B Then it is impossible to have the following commonly needed panel setup: Left: Parent Page showing Child pages. Right: Child Page showing Description. So easy navigation of child pages is not possible, because as soon as I choose the tab with Descirption field in a child, the parent page also switches to Description tab. I hope the automated selection can take care of this soon. ---
**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\ **Post date:** [May 22, 2025, 4:41pm UTC](https://community.fibery.io/t/done-multiple-entity-views-automated-selection/7554/9 "2025-05-22T16:41:02Z")
> [@mdubakov](#): > > we do want to go for field → default entity view in future Any general timeline on the ability to set an entity view dynamically based on a entity field/current user? We’re trying to sell Fibery as a potential custom CRM/ERP solution to our clients but keep running into scenarios where the lack of context filtering/dynamic views is a deal breaker. It’s common in many industries to have multiple people needing to contribute/collaborate on a project, but not all of their roles are the same and it’s virtually impossible to maintain an accurate, secure source of truth in Fibery when viewing and editing permissions are an all or nothing option. Like, it’s not out of the ordinary for a manager to need to see and edit fields that a regular employee shouldn’t, right? Dynamic entity views based on field values, along with [Field-Level Permissions](https://community.fibery.io/t/field-level-permissions/2799) & [Field Locking](https://community.fibery.io/t/lock-fields-to-avoid-accidental-editing/8490) are essential for many businesses to seriously consider Fibery as a solution. ---
**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 22, 2025, 5:36pm UTC](https://community.fibery.io/t/done-multiple-entity-views-automated-selection/7554/10 "2025-05-22T17:36:55Z")
Field-level permissions will not be happening any time soon (years, probably). In the meantime the workaround is to split fields across (linked) databases, and use lookups to surface field values from one db in the entity view of the other, if necessary. Assuming that the ability to view/edit fields in related entities gets delivered, the UX for this will potentially be good enough to satisfy most use cases. See [here](https://community.fibery.io/t/editable-lookup-fields/8424) and [here](https://community.fibery.io/t/joins-include-related-entitys-fields-in-views/1966) and maybe other topics. Dynamic entity views will likely happen at some point, just no ETA, and will also likely contribute to making the linked-dbs-to-implement-field-permissions workaround even nicer. ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [May 22, 2025, 11:36pm UTC](https://community.fibery.io/t/done-multiple-entity-views-automated-selection/7554/11 "2025-05-22T23:36:02Z")
The drawback to this approach is that we (still) cannot EDIT linked fields without going to the linked entity page. ---
**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 23, 2025, 6:07am UTC](https://community.fibery.io/t/done-multiple-entity-views-automated-selection/7554/12 "2025-05-23T06:07:18Z")
> [@Matt\_Blais](#): > > The drawback to this approach is that we (still) cannot EDIT linked fields Indeed, but I did say > [@Chr1sG](#): > > Assuming that the ability to view/edit fields in related entities gets delivered 👍 ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [September 18, 2025, 2:02pm UTC](https://community.fibery.io/t/done-multiple-entity-views-automated-selection/7554/13 "2025-09-18T14:02:35Z")
This feature was released today, please check [September 18, 2025 / ⚔️ Specify which Entity View to open based on some field value](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616) ---
**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 18, 2025, 2:26pm UTC](https://community.fibery.io/t/done-multiple-entity-views-automated-selection/7554/14 "2025-09-18T14:26:11Z")