Forum Discussion
PBI Server May 2020 not refreshing saved reports
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.
I also noticed that RLS stopped working. Does anyone have a similar problem?
Super User
Strangers wrote:
I also noticed that RLS stopped working. Does anyone have a similar problem?
I just setup a new file with RLS, deployed it and added myself to a role and it worked fine. What specific issue are you seeing?
As with data, this works for newly created reports.
But I added the RLS to the existing report and updated it manually. As well as for the data in the report, there was a certain delay in time (about 1 hour) after which the RLS began to work.- d_gosbell
Strangers wrote:
As with data, this works for newly created reports.
But I added the RLS to the existing report and updated it manually. As well as for the data in the report, there was a certain delay in time (about 1 hour) after which the RLS began to work.Ah so that's probably related to the data issue. It appears that somehow the server holds on to an old copy of the data model in memory. And the data model contains the role definitions. Things like a scheduled refresh or a restart of the service can force the updated data model. So if you have an hourly scheduled refresh this might explain this, or their could be some other form of timeout which eventually flushes the old version of the data model out of memory.
Unfortunately, scheduled refresh is not working, I will make a new post for this issue.
The workaround is ok, hope there will be new version soon. Restarting server is also a good option, for the moment this is the chosen method - update manually all reports, then restart the server.
So, the only workaround is to return to Jan 2020 version?
Is it safety just to install the older version?- d_gosbell
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.