Hi,
We have recently had an issue with a paginated report parameter which was changed in the Power BI Paginated Report Builder, however the change seemed to disappear a few weeks later.
The sequence of events is:
1. The report was created in Power BI Report Builder and published to the Power BI Service
2. The user requested a change to the report parameter which was done in Power BI Report Builder
3. The amended report was published to the Power BI Service over the top of the existing report
4. The parameter was updated successfully and the user had been using the report for approx. 3 weeks.
5. Yesterday the report was once again showing the original parameter configuration
Yesterday I was able to download the .rdl file from the Power BI Service and open it up in Power BI Report Builder to confirm the parameter was correctly updated therefore i cannot explain why its showing different values in the Power BI Service.
I deleted the report from the workspace and re-published it and it does now show the correct values.
Can anyone explain this behaviour?
many thanks
Hi,
Yes i've tried refreshing the dataset used by the report, and clearing the browser cache both in Chrome and Edge and this makes no difference.
We have a version in a TEST workspace which has the same issue.
The issue seems to be the parameter is still pointing to the old field and publishing over the top of the report does not update it, only deleting the report and recreating it seems to fix the issue.
Really sorry for the late reply. But it seems difficult to explain this behaviour, you can create a support ticket at : https://powerbi.microsoft.com/en-us/support/to get technical support.
Best Regards,
Community Support Team _Tang
If this post helps, please consider Accept it as the solution to help the other members find it more quickly.
Did you refresh the report at that time? Does the report still show the old parameters after refreshing?
In fact, if the new report successfully replaces the old one, the old parameters will no longer appear. Please try to clear the browser cache, etc.
Best Regards,
Community Support Team _Tang
If this post helps, please consider Accept it as the solution to help the other members find it more quickly.