NOTE: this article explains how data refresh works in the 1.5 through 1.8.1 releases, however in the 1.8.0 release "Summaries" were renamed "Scaled Reports" as part of the new Scale Report workflows that were introduced.
How Does Refreshing Data Work?
VividCharts can refresh data in two different ways on a View, Summary, or Report Generator View:
Daily - A scheduled job that runs daily
On-demand - Data refresh can be triggered manually by a user with the appropriate roles and access.
Who can configure the frequency of the data refresh?
View - A user with the builder role and edit access to the view.
Summary - A user with the builder role and edit access to the summary.
Report Generator View - A user with the admin role and View access to the View.
| Role Required | Access Level |
View | Builder | Edit |
Summary | Builder | Edit |
Report Generator View | Admin | View |
Who can refresh data on demand?
Beginning with the 1.5 release, a new role was introduced called Refresher(x_vivid_vc_core.refresher). The x_vivid_vc_core.refresher role is required for a user to be able to refresh data on demand for any VividCharts asset. The following conditions are required for a user to have access to on-demand refreshing.
| Roles Required | Access Level | Logged In |
Entire Summary List | Edit Access on the Summary | Yes | |
Filtered Summary List |
| View access on the Summary | Yes |
Set | View access to the Summary | Yes | |
Summary View | View access to the Summary | Yes | |
Multi-Summary View (click "Open in Viewer") | View access to the Summary | Yes | |
Regular View (not part of a summary) | View access to the View | Yes | |
Report Generator View | View access to the View that was generated | Yes |
What are the levels of the data refresh?
Data refresh can be set on different levels of the VividCharts application. With these different levels comes different behavior when the on-demand data refresh is triggered.
Summary List - All views within that Summary.
Filtered Summary - All views within that Summary that meet the current configured filter conditions.
Set - Only Views contained within the Summary Set. For example, if a summary contains 10 Summary Views and a set is created from that summary that only contains 2 of the Summary Views, refreshing on the Set level will only refresh the 2 Summary Views contained in the Set. The other 8 Views in the Summary will not have their data refreshed.
Summary View - The single Summary View currently being viewed.
Regardless of the level of refresh, new data will be gathered via a live query.
How do I know when data has been refreshed?
Depending on the object being viewed, timestamps can display in different locations showing the date and time of the most recent refresh. However, a newly created view will not have a timestamp until its data is refreshed. Timestamps will also not appear in edit mode.
On a View the timestamp will be in the top right corner.
When a refresh is in progress, it will indicate who triggered the refresh.
When available, the data will be injected into the View automatically and the timestamp will update. The "New data loaded" tag will disappear after 5 seconds.
On the cards of a Summary List View hovering over the icon will display who executed the refresh.
