- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Report visuals not loading in PBI service
Hello all,
I have a report where the visuals are not loading results and just continues to spin. This only became an issue today, the report was fine yesterday. The report is in its own workspace (with other reports) that is connected to a semantic model in a separate workspace (with other models). All of the other reports in the workspace work as expected, we are only experiencing issues with the one report.
We have tried manually refreshing the dataflows/semantic model, clearing the cache in the model then publishing it to the service, and publishing the model to a different workspace (which worked).
I'm wondering if maybe there is an internal/transient issue that I'm unaware of. Any help is greatly appreciated!
Thanks,
Mark
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @MarkRMoran01 - check on the problematic report in Power BI Desktop.Refresh the connection to the semantic model and check if the data loads successfully.Re-publish the report to its workspace to see if the problem resolves.
Try refreshing the dataset in Power BI Service manually and check the refresh history for errors or delays.
Look for heavy or inefficient measures in the report. They might be causing delays or timeout issues. Simplify calculations if possible.Ensure that report-level or visual-level filters are not overly restrictive or returning no data.
Since the report relies on a semantic model in another workspace, latency or network issues between workspaces could cause spinning visuals. If publishing the model to another workspace resolves the issue, this could point to a backend issue.
Please check the above troubleshoot activities and i hope it helps.
Proud to be a Super User! | |
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Glad to hear that you've solved this problem!
After my search, I didn't find a similar issue on the internal platform.
Given the lack of the information, I speculate that it could be that your PBIX file has undergone an unexpected corruption. This could be caused by caching, network issues, data sources, or other issues.
Best Regards
Zhengdong Xu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Glad to hear that you've solved this problem!
After my search, I didn't find a similar issue on the internal platform.
Given the lack of the information, I speculate that it could be that your PBIX file has undergone an unexpected corruption. This could be caused by caching, network issues, data sources, or other issues.
Best Regards
Zhengdong Xu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @MarkRMoran01 - check on the problematic report in Power BI Desktop.Refresh the connection to the semantic model and check if the data loads successfully.Re-publish the report to its workspace to see if the problem resolves.
Try refreshing the dataset in Power BI Service manually and check the refresh history for errors or delays.
Look for heavy or inefficient measures in the report. They might be causing delays or timeout issues. Simplify calculations if possible.Ensure that report-level or visual-level filters are not overly restrictive or returning no data.
Since the report relies on a semantic model in another workspace, latency or network issues between workspaces could cause spinning visuals. If publishing the model to another workspace resolves the issue, this could point to a backend issue.
Please check the above troubleshoot activities and i hope it helps.
Proud to be a Super User! | |

Helpful resources
Subject | Author | Posted | |
---|---|---|---|
01-08-2024 05:00 AM | |||
10-17-2024 09:03 AM | |||
07-03-2024 10:01 AM | |||
10-28-2024 03:05 AM | |||
03-16-2024 02:39 AM |