This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
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.
Solved! Go to Solution.
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.
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.
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.
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.
Thanks for the detailed response. Can you tell me where the cache management settings are located in Report Server? I couldn't find them in Configuration Manager.
Hi @ReyCarter_777 ,
The cache and execution settings are not available in Configuration Manager; they are managed through the Power BI Report Server web portal. To adjust these settings, open the report in the portal, select Manage from the three dots menu, and review the Processing Options or Execution section.
Ensure the report is configured to run with the latest data, not from a cached version or snapshot. If caching is enabled, consider disabling it or clearing any cached instances, as this may address the issue you are experiencing.
Thank you.
I don't have such items in Report Server. Can you send me a screenshot?
What is your server version? and what is the account's server role? Is this a .pbix file or a Report Builder file?
Hi @ReyCarter_777 ,
This issue in Power BI Report Server is usually related to version compatibility, file type, or permissions, so please ensure the report is created using the matching Power BI Desktop for Report Server version as a mismatch can block updates or publishing, also confirm whether the file is a .pbix or .rdl since they are handled differently, and verify that your account has Publisher or Content Manager role at the folder level which is required to update reports.
Refer these Microsoft docs:
https://learn.microsoft.com/en-us/power-bi/report-server/changelog
https://learn.microsoft.com/en-us/power-bi/report-server/row-level-security-report-server
Thank you.
I didn't understand your answer. Initially, said it was about caching. Showed a screenshot (I don't have such items as subscriptions, caching, or snapshot history in my power bi .pbix Report Server. Now, the problem may be in the version, file types, and permissions. Although our versions are all the same, the files are.pbix, maximum permissions. I like the first reason I mentioned about the cache, but I don't see how to fix it.
Hi @ReyCarter_777 ,
Thank you for the clarification it helps clear up the confusion. In Power BI Report Server, features such as subscriptions, caching, and snapshot history are available for paginated reports (RDL), but these options may not be visible for .pbix reports. For .pbix reports, the recommended method is to refresh the data in Power BI Desktop and then republish the report to Report Server to update it. Please ensure the report has been refreshed, redeployed, and that you are viewing the latest published version.
Thank you.
Colleagues from Microsoft, I ask for your help in solving this incident.
Currently, there is a pbix dashboard that opens empty when updated, and this happens every morning (even though the scheduled update shows a successful status).
What is the reason for this, and how can it be fixed?
We have tried resaving, updating the model, and playing with permissions and updates, but none of these solutions have worked.
It is surprising that this issue only affects one dashboard, as we have not encountered similar problems with other dashboards.
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
| User | Count |
|---|---|
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 |