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.
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.
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.
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.