The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
I've been sharing the same report with a few dozen users for most of this year. This last week is the first time I'm seeing this issue.
One of the table views typically will refresh as a user engages a slicer elsewhere on the page. However, as of this last week, in the scenario where the resulting table is null (i.e. there are no resulting records under the newly selected filter context), instead of displaying an empty table as expected, the table just stays as-is (i.e. doesn't refresh).
We don't see any issue in the scenario where the resulting table is NOT empty... it refreshes properly in this case.
I don't see this issue in my Power BI Desktop version of the model, it only occurs when folks are browsing the report via the Power BI cloud service.
I stumbled across a workaround to get it to refresh... I notice that when I switch to a different report page, and then come back to the page with this issue, the tables will then be refreshed properly to show an empty table as expected. Although this is not a good workaround since it can be cumbersome to jump back and forther between tabs simply to refresh a table.
Thanks.
Jason
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.