Forum Discussion
Problem with updating the Power BI Report Server dashboard
Problem with updating the Power BI Report Server dashboard (Version: 1.21.9032.4573 (build 15.0.1116.121), released: September 26, 2024) One report is successfully updated with the Completed Data Refresh status. However, when the dashboard is opened, the data is not loaded, and the report is empty. How can this be resolved? There are no errors, and the data is physically present in the database tables, but the report itself is empty.
It turned out to be much simpler. Friends, it turns out that updating data in SQL Server takes longer, and the dashboard simply connects when the data in the final table is not yet ready. Therefore, it is empty. The issue has been resolved.
13 Replies
This is a known quirk with Power BI Report Server the refresh succeeds but the report shows stale or empty data.
Report Server caches rendered reports. Even after a successful refresh, users may see a cached (empty) version. Try opening the report with ?rs:ClearSession=True appended to the URL to force a fresh render. You can also check the cache settings in the Report Server portal under the report’s properties.
- The fact that the problem is known does not make it a solved problem. Dashboards on the server are opened by business users, it is unlikely that they will add something to the link. Is there a solution? Maybe some settings on the server will help solve it?
Hi ReyCarter_777 ,
The issue you're experiencing is related to how Power BI Report Server manages report execution and caching, rather than the data refresh itself. When a dataset is refreshed, it updates the underlying data, but users may still see a cached or previously rendered version of the report, which can appear empty even though the data exists in the database.
Since users access the report directly from the server, using URL parameters is not an effective solution. Instead, it is advisable to adjust the report’s execution settings in the Report Server portal to ensure it always retrieves the latest data. Review the processing or execution properties and configure the report to run with the most recent data, avoiding cached copies or snapshots.
If caching is enabled, consider disabling it or synchronizing its expiration with your data refresh schedule to prevent outdated results. After updating these settings, clear any existing cached instances, as an empty version may already be stored. Once the execution settings and cache are updated, the report should display current data for all users without requiring manual intervention.
Thank you.
It turned out to be much simpler. Friends, it turns out that updating data in SQL Server takes longer, and the dashboard simply connects when the data in the final table is not yet ready. Therefore, it is empty. The issue has been resolved.
