Forum Discussion
PBI Server May 2020 not refreshing saved reports
- 6 years ago
Anonymous wrote:
So, the only workaround is to return to Jan 2020 version?
Is it safety just to install the older version?So one workaround is open your report in desktop, then go back to the portal and delete the file from there before you save. But that is not great for end users.
Otherwise you either have to wait for a fix or look at going back to Jan 2020. Although Ideally you should restore the ReportServer database from a backup as I'm not sure if the May release made any schema changes or not.
Realistically my guess is that it could be at least a week or two, maybe longer before an update is published. Even if they have a fix for this today Microsoft will need to do a full test run to make sure that the fix does not break anything else. The last thing they want to do is rush out a fix that breaks something else.
Anonymousif you mean Refresh All in Query Editor, i have tried but no success.
No, try a 'Refresh All' on the Report view.
- josef786 years ago
Memorable Member
Anonymous 'Refresh All' on the Report view does not help for this issue. It is not affecting out of date SSAS cache.
SSAS cache (on PBIRS instance) is not reloaded (if already loaded in cache) for used PBI report on PBIRS after data are updated in DB (on MSSQL instance), does no matter if data are updated from PBID or Scheduled refresh.
- Anonymous6 years agoNot applicable
josef78 thanks for confirming issue, this does seem to be a separate issue altogether.
I just thought on the off chance that the workaround solution we found may have applied to your situation, unfortunately it has not.
- d_gosbell6 years ago
Super User
I've just heard that a hotfix for this issue has been released. I've done some testing in my environment and as far as I can see this issue appears to have been fixed. The new version is 15.0.1103.232 and they've just updated the may 2020 download at https://aka.ms/pbireportserver so if you re-download from there and re-install it should update your server. (you can check which version you are currently running by going to the http://<yourserver>/reportserver endpoint)