When creating a new field in a database, the new field appears in ALL Entity Views (all tabs). As a result, I need to remove the field from all Entity Views except from the one I want the field to show. I think that as good as nobody will need a new field to appear in all Entity Views. At least I never encountered that need. Removing the new field from all Entity Views is a lot of work each time. Related: Also, when creating a new Entity View, it includes ALL fields. That is a lot of work to remove the fields, since the purpose of an Entity View is to focus on a clean view. Although a workaround is to clone an existing Entity View, it is not intuitive and I often end up deleting new Entity Views in order to clone an existing one. So, the expected/desired behavior would be: When Adding a new Entity View, do not populate it with any fields (or only with the default Entity View fields) When creating a new field, do not include it in every Entity View.

Implemented in latest release [image] September 24, 2026 / french_fries Better tables in Rich text, See where a field is used before you delete it Changelog Our designers have started coding! Beware! french_fries Better tables in Rich text Working with tables in documents just got a lot smoother: Drag to reorder rows and columns. Hover over the left or top edge of a table to reveal a grip. Hovering it highlights the whole row or column. Click to select it and open the menu, or drag to move it anywhere in the table. Right-click for everything. Right-click any cell to select it and open a menu with all table actions. Colorful cell highlights. The…

These features are in our backlog

I find it very counter-intuitive that a field I create somewhere just pops up in all entity views.. Usually you create an entity view with a specific purpose. If I want to edit an entity view, I will do just that. Just because I created a new field it doesn’t mean it belongs to all entity views. In my opinion default behavior should always be to enable the field only in the view where it was created.

+1 I noticed this happening far more often now that I’m creating more complex reports and and connections especially with AI via MCP. Because there are often a bunch of helper fields created for the purpose of the report/view and then have to go through every View and remove the newly created fields If I’m in UI and add a field from the View itself, then yes visible. Otherwise not visible on any other view I would need to enable it on each view Oh and also just noticed this could merge? Do not add a new field to ALL Entity Views

[DONE] Do not show new fields in existing entity views

Ideas & Features

mdubakov September 24, 2026, 1:52pm 5

Implemented in latest release

Topic		Replies	Views
[FIXED] New Fields Automatically Pollute Multiple Entity Views Bugs & Issues	3	104	September 24, 2026
[DONE] Quickly Hide All Fields in Entity View Ideas & Features entity-view	4	167	January 15, 2026
Hide fields and views tab on entity for non architects Ideas & Features entity-view	6	130	September 24, 2026
Hiding field from Entity View hides it also from other Entity Views Bugs & Issues entity-view	2	56	November 20, 2025
[DONE] Multiple Entity Views - automated selection 😀 Ideas & Features entity-view	12	373	September 18, 2025

[DONE] Do not show new fields in existing entity views

Related topics