Strategy One
Enabling Unified Data Refresh in Projects
Starting in Strategy One (September 2025), a new project-level property allows cube-based dashboards and documents to display updated data only after all cubes in the project have completed their scheduled refresh. This synchronization improves data consistency across visualizations, even when cubes finish refresh at different times, ensuring more reliable analysis and decision-making.
This setting does not apply to manually published cubes and is only effective for dashboards and documents executed interactively. Reports executed in Library also benefit from this feature.
This feature is disabled by default and can be enabled by setting the project property 'Hold data updates until all project cubes complete refresh' in Workstation.
Enabling in Workstation
- Open the Workstation window with the Navigation pane in smart mode.
- In the Navigation pane, click Environments.
-
Log into your environment.
You must have the Configure caches privilege.
-
In the Navigation pane, click Projects.
-
Navigate to the project, right-click and select Properties.
-
Click All Settings, enter hold data in the search box, or scroll to the Hold data updates until all project cubes complete refresh setting.
-
Enable the setting.
-
Click OK.
-
Reload the Project or restart the Intelligence Server.
Considerations
-
Schedule refreshes to avoid overlapping cycles as overlap may cause delays or outdated data.
-
Cube memory usage and performance counters, such as "Number of Intelligent Cube Caches In Memory", may temporarily increase during the refresh window. This increase is due retained cube versions. After the refresh completes, memory usage and performance counters will decrease to expected values.
-
If the Intelligence Server detects potential data inconsistencies during refresh window, users can reopen the dashboard for updated results.
-
During the refresh window, reloading cubes from disk updates dashboard data. Ensure adequate memory is reserved for cubes, such as enabling "Load Intelligent cubes on startup" and "Load Intelligent Cubes into Intelligence Server memory upon publication" to minimize unexpected cube reloads.
-
A cube that completes its own refresh shows an updated "Last Refreshed" time in the Cube Monitor. You cannot manually refresh while waiting for other cubes in the same scheduled cycle.
-
Avoid restarting, stopping, joining, or removing Intelligence Server nodes during cube refreshes to prevent data inconsistencies.