If the entity-view variation to be displayed can be determined by a field/formula/filter, including WHO is viewing, and what groups/roles they belong to - that would be amazing
and yes, it would go a long way to answering my need for polymorphism.
Some old related threads:
This would be one way to accomplish something like hierarchical types/mixins: we have a single âparent Typeâ that includes all the fields for all of its various sub-types, plus a Single Select field to choose a specific type.
Then for each entity, its entity view would be customized by hiding the fields that are not relevant for its particular sub-type.
If we get Customizable Entity Views, I imagine that would accomplish this neatly.
I think itâs not a problem if all fields are always available in all other Views (besides Entity Views), because we already have the ability to customize those views and exclude certain fields.
But this ability would be very useful in Entity Views - if we could conditionally display Entity View fields, customized for each entity, based on the value of a single-select field, that would be a good solution to this issue.
Perhaps we could have the ability to add to each field in a Type, a formula,âŚ
A more general solution would be the ability to customize entity views, which I think is in the pipeline already.
This would be great
And I would add, it would also be super useful if the âdefault viewâ for a particular entity could be defined by a formula. So the âview selectorâ would have an entry for each manually created named view, plus one for âAutoâ (a formula), and another for âShow All Fieldsâ.
Also, regarding the current ability to hide fields (which is awesome) â I would find it very helpful to have a âShow All Fieldsâ toggle in the fields selectors, which would TEMPORARILY (and onlâŚ
2 Likes