It would be very helpful that each Entity View has a direct link with URL, and that Mention Links can open the corresponding Entity View directly.
Why:
Sharing direct links to an Entity View helps team members as well as stakeholders directly acccess the content needed, without losing context of the entity it belongs to.
Example 1:
I want to share a link to all offerings of an organization to a client, but keep the context (other entity views) of the organization visible for the client.
The Offerings Entity View contains fields:
Products
Services
Programs
Support
Sharing a List view with nested databases would isolate the information to Offerings, which cuts out context of the entity.
Example 2:
Team members need to often access different Entity Views of a Project directly, without having to navigate the entity view tabs to find what they need. Such as:
The ‘Sprints’ Entity View cotains fields:
Active Sprints
Sprint Planning
Sprint Issues
Example 3:
Sharing a SupportTickets entity view of a certain Contact, while you want the context of the contact entity to be easily accessible.
Without Entity View links, these actions require much more digging in entity views each time.
The ability to set what multi-entity view a user will open when sharing a link. Right now we need to tell people to open it, then change the view in order to see the thing I’m talking about. If we had the ability to send with a set view, this would make it easier for people we collaborate with.
Yes, our issue is that we have a preference for how an entity is viewed externally (very limited in what fields are included) and what the default view should be for workspace users. Currently, for both groups the default is “first view in the list”. I’d love to be able to set which view to share (or perhaps a URL per view?), then the first view in the list can be the default for workspace users.
Likely a low effort - high benefit implementation?
I often need a direct link to an entity view. For example sharing an entity view for a visitor. Or my personal entity view.
This is currently not possible because entity views aren not entities (yet).
The most obvioius workaround, is URL parameters (../?field-name=…) which would set a value to an entity field, and if that field is used in an entity view rule, it should redirec to that entity view.
In Fibery, URL parameters to fill field names is already possible in urls of forms. So it should theoretically be possible with entity fields also.
