# Entity View Tabs should not Synchronize across entities of the same database

**URL:** <https://community.fibery.io/t/entity-view-tabs-should-not-synchronize-across-entities-of-the-same-database/9251>\
**Category:** Bugs & Issues\
**Tags:** entity-view\
**Created:** [July 21, 2025, 10:23pm UTC](https://community.fibery.io/t/entity-view-tabs-should-not-synchronize-across-entities-of-the-same-database/9251 "2025-07-21T22:23:27Z")\
**Posts on this page:** 4\
**Page:** 1

<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:** [July 21, 2025, 10:23pm UTC](https://community.fibery.io/t/entity-view-tabs-should-not-synchronize-across-entities-of-the-same-database/9251/1 "2025-07-21T22:23:27Z")

</div>

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?

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/b/bd4cf46cd14623100364621666b0a938e1c52fd9.png)

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/c/ccfdc89f9f19e3141fd8d3312d02ec1b4997b06c.png)

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/a8ba975320ccf7e51f7913c6008707edfbbc8f4b.png)

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/e14d7e86f7ae9ab967109e46f114972f96ccf282.png)

---

<div class="post-metadata">

**Author:** ![AdVhPkgKad](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\
**Post date:** [July 22, 2025, 4:58am UTC](https://community.fibery.io/t/entity-view-tabs-should-not-synchronize-across-entities-of-the-same-database/9251/2 "2025-07-22T04:58:50Z")

</div>

I don’t think it’s a bug, because it’s very likely that the functionality is intentional - that being: stored as an account variable per database

This is because when you leave and come back, it’ll remember which tab you were on

Potentially a solution would be to allow administrators to turn this off globally, enforcing context views to open on the default (first) tab, and not write back the last opened view

* * *

And not to hijack your thread, but something similar could happen with global filters, since the users I’ve dealt with in the past week complained about all filters being applied by default when they first enter a view

---

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [July 22, 2025, 7:04am UTC](https://community.fibery.io/t/entity-view-tabs-should-not-synchronize-across-entities-of-the-same-database/9251/3 "2025-07-22T07:04:57Z")

</div>

I think this might be solved in the upcoming “Use rules to set which entity view opens”

If the rule is “Has parent” it should open the content, is it has children, it should open the lost view.

Maybe. Let’s see.

---

<div class="post-metadata">

**Author:** ![danielbmarsh](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/danielbmarsh/32/13104_2.png) [@danielbmarsh](https://community.fibery.io/u/danielbmarsh)\
**Post date:** [July 29, 2025, 5:15am UTC](https://community.fibery.io/t/entity-view-tabs-should-not-synchronize-across-entities-of-the-same-database/9251/4 "2025-07-29T05:15:59Z")

</div>

I agree that it’s unexpected behavior for an open page to suddenly switch tabs when you were working on another panel.

And I can’t think of a good use case for it to behave as it currently does. It seems like the variable that sets the default should only be pulled in when the entity is opened.
