Name as draggable field in Entity View (to allow fields above it)

Persistent Context

The suggestion is based on the need of a persistent context section in the Entity View, which is in our view the biggest weakness of Fibery entity view UX (navigation sidebar is not suitable for that, too high level and confusing, and the breadcrumb navigation drops context out of reach).

Having the Name as a draggable field like any other field, would serve the needs in the following very common use cases:

Persistent parent menu

Placing a field above the Name, which represents a parent entity such as a Project or Department. The visual logic is that everything below and including the Name relates to the entity itself, and what is above it, relates to parent entity/entities.

For example, when we want a persistent project menu that appears at the top of each child entity, we want that to visually distinctive by placing it above the entity name. This could include for example a relationship collection field that shows projecte menu items or project categories.

Notifications and user operations

Another use case is that the area above the Name can be used for Notifications and User operations. I am currently heavy user of a Notifications field, that allows for warnings, real time messages, as well as all interactions with the user, such as operations/automations, a personal persistent menu, for quicklinks and focus entities, etc.

Beyond workarounds

The feature requested above is actually partly a workaround for the lack of a dedicated panel for persistent contextual data. It would be beneficial to have that present across different databases/entities. Currently I have to add such parent menu to each database and keep them manually the same, not very efficient.

Concluding, this is a strong improvement suggestion for when you guys start working on Entity View. Thank you.


What do you mean by ‘a Notifications field’? Is it just a text field that you populate with automations? Or a formula field?

YES, this would be amazing. This is a pain point for my team as well, as it’s easy to miss a parent entity relationship amongst the other relationship fields below the name.

1 Like