How to Set Auto-refresh for Dashboard and Data Screen
Brief Operation Description
Auto-refresh for direct connection dataset/universe dataset cards requires the frontend (dashboard/data screen) to turn on the "Auto-refresh" switch + check "Support real-time card data" in the dataset.
Other datasets are not suitable for auto-refresh scenarios.
Specific Operations
Frontend Auto-refresh Switch
For dashboard or data screen, turn on the "Auto-refresh" switch.
When this switch is turned on, it means the system will automatically refresh the page at regular intervals to get the latest data.
Frontend Page Refresh Frequency
For both dashboard and data screen, page refresh frequency can be customized in Administrator Settings — System Management — Real-time Settings.
Note: The dashboard real-time refresh frequency is consistent with the default cache validity period for direct connection datasets in real-time state.
Dataset Real-time Refresh Settings and Frequency
- Direct connection dataset, universe dataset
- Switch:
When creating a new dataset or on the dataset details page, in the data update section, you need to check "Support real-time card data".
- The real-time nature of data is related to cache validity period.
The default cache validity period can be customized in administrator settings. You can also choose no cache, then access the database to read the latest data each time.
- Other datasets
Such as database-extracted datasets (guanindex), file datasets, ETL output datasets, cloud application datasets, card datasets, view datasets, are not suitable for auto-refresh scenarios, and there are no real-time configuration items in the dataset.
If the "Auto-refresh" switch is turned on in the dashboard/data screen, then each time the frontend page refreshes, the data obtained is the most recently updated data of the dataset.
When does the page see data? Here's an example
If the default cache validity period for direct connection dataset is 5 minutes, and the dashboard refresh frequency is also 5 minutes.
Dashboard first refresh, database query, generate cache 1002
caseA
10:04 Manual page refresh (no filtering, linkage, drilling operations), data seen — cache 1002 (because the query logic is the same as 10:02)
No operation, 10:08 data seen — cache 1007 (dashboard 10:07 refresh updated data)
caseB
10:04 Manual page refresh, data seen — cache 1002
10:05 Filter condition switch, data seen — database query, generate cache 1005 (with filter condition)
No operation, 10:08 data seen — cache 1007 (dashboard 10:07 refresh updated data with filter condition)
Other Issues with Direct Connection Refresh
Q: Why is the extracted dataset data update cycle, while the direct connection dataset is cache validity period?
A: The extracted dataset data is stored in BI, while the direct connection dataset BI doesn't store data, and queries the database each time.
Q: Since it's a direct connection, each query goes to the database to get data, why is there still a cache?
A:
Q: Why does the same large screen not refresh when opened with Edge browser, but Chrome can refresh?
A: The real-time switch is stored locally in the browser. When viewing pages with different browsers, you need to turn on the browser's real-time refresh switch again.
Additional notes: After the "Auto-refresh" switch for the data screen is turned on;
b. For direct connection datasets set to no cache, real-time polling is performed according to the "Data Screen Real-time Refresh Frequency" setting;
c. For other datasets, based on their card data, timed polling is performed according to the setting in "Real-time state, direct connection dataset default cache validity period".