Forum Discussion
Power BI Service Report not Refresh Properly
Hi v-aatheeque,
Please see below.
- All visuals are affected.
- The model type is Import.
- The workspace is on Premium capacity.
- The report is only on a workspace not app, but I just created an app to test it and the visuals are not updated in the app either.
- I'm not sure what the hard refresh mean. But if I open th ereport via desktop and republish it, the latest view/data will show in the workspace. No refresh from the workspace worked.
I've tried the following:
- dataset level "Refresh Now"
- Ctrl + Shift + R
- In the report, click "Refresh visuals"
- In the report click return to the default view
- No incremental refresh is set up in the report.
- Pleasee see the below screenshot, I've covered sensitive information.
View in the workspace:
View in the desktop once opened:
Thanks a lot for your time and help.
Hi JoJo_001001
Thanks again for the detailed information.
Based on the behavior, this appears to be related to caching at the capacity level.
Could you please check with your Power BI/Fabric admin:
- Whether Query Caching is enabled or disabled in the Premium/Fabric capacity
- If possible, try toggling the setting (ON → OFF or OFF → ON) and then refresh the report.
Note : You need Power BI Admin / Capacity Admin access.
This will help confirm whether cached query results are causing the visuals to remain stale.
- JoJo_0010014 months agoNew Member
Hi,
We switched to the premium capacity when investigating this issue, and have tried in the Semantic Models -> Query Caching, turn it on an off, it's currently set as "Capacity default: query caching Off". No luck.
- v-aatheeque4 months agoCommunity Support
Hi JoJo_001001
Thanks for the update and for trying the suggested steps.
Since the dataset refresh is completing successfully and the latest data is visible in Desktop, but not in the Service even after testing query caching and multiple refresh methods this behavior appears to be related to caching or rendering at the service/capacity level rather than the dataset itself.
As the issue persists across users and visuals, the next step would be to raise a Microsoft Fabric Support and Status | Microsoft Fabric ticket for further investigation from the backend.