When users configure reporting widgets in Vizibl dashboards they are presented with options that determine how the data is aggregated and presented in their widgets. For example, users reporting on projects with a certain status in a widget across relationships of different categories and segments will be asked to select the applicable filters individually as part of the widget configuration.
Currently, in the platform, saved views are supported across the majority of lists; Projects, Opportunities, Relationships, etc. They are used as an easy way to retain desired filters that can be applied to a list in one click. Saved views can also be shared between relationships, users, and the owner’s own organization or company, thus allowing additional users to apply the same filters to their lists. Read more about creating a saved view
Using saved views in reporting
With the release of saved view support in Reporting, any data type that supports saved views in the platform will now allow you to filter the data in your reporting widget based on using one of your saved views. Example: a Saved View of Projects can be used in widgets that use Projects as the main dataset.
How it works
On Reporting, navigate to a data type that has a corresponding list that supports saved views; Opportunities, Projects, etc. On the first page of widget configuration for each of these widgets, you will be asked whether you would like to add your filters manually and create a widget without a saved view, or whether you would like to select a saved view of that data type (in this case, Opportunities).
2. When a saved view is selected, it is displayed as one filter, even though it holds many filters inside.
3. When any type of saved view is selected, it can be cleared by selecting the ‘Clear saved view’ button if it is no longer desired. This will clear the saved view selector back to the default empty state.
When your saved view is used on a shared dashboard, you cannot delete the widget unless you manually remove it from all dashboards.
Visibility in dashboards using saved views
When saved views are used in Reporting dashboards, creators are responsible for the filters that get applied and affect the data returned. For this reason, it is incredibly important that when a saved view is no longer used, all widgets that depend on that saved view are checked first before the saved view can be deleted.
This protects your dashboards from accidentally displaying data in a different context to the users of those dashboards. This means that users will have to manually remove or replace their saved views in all Reporting widgets before the saved view can be deleted or made private. Any saved view that’s used in a shared dashboard is implicitly shared.
Why you should use saved views
Increased speed of creating widgets.
No need to edit widgets to change the data as the user can edit the saved view instead, meaning the data in the widget is consistently updated.
An effortless way to share saved views between dashboard viewers/editors