- Systems grow over the time and it’s hard to control retirement process for old views, especially for large implementations. As a result, list of available system views tend to grow out of control.
- If record is required on multiple customized sub-grids, chances are each sub-grid will potentially require yet another system view.
- Remove views that are broken for a user/team. Your view may include fields from a parent entity users do not have access to. They will see “You do not have permissions…” error plastered all over the grid.
- Simplify UI and provide better experience for the end-users. Tailor their experience by role and only show views that are applicable for their role.
- When users ask for a new “report”, quite frequently they mean “give me the list of records satisfying certain criteria”. A.k.a. view.
Lucky for us, views can be shared:
- Create a handful of universal views that make sense for everyone, e.g. “My accounts”, “Overdue invoices”, and implement them as system views
- If you would like to restrict view to a specific user/team, create a personal view and then share “read” access to it with the user/team.
The only drawback of this approach is that users will see these “private” views under “My Views” subheading. Oh, and you won’t be able to use these views in system charts/dashboards, or subgrids.