Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hi All
There is a bug in the Online Power BI Service where Matrix visuals (both old and new matrix styles) do not display ‘no data’ states correctly when filtering the Matrix using a slicer.
i.e. If the Matrix is filtered so that it contains data, there is no problem. If the slicer filters the Matrix so that it should not contain any a data, the Matrix does not transition to a state showing no data, but continues to show the data from the way the Matrix was previously filtered.
I have published a stripped down/fictionalised version of my original report here:
As well as provided the PBIX file here:
https://drive.google.com/open?id=0B-TK-K5EDIWNYmtkVllOaEQ3SXc
Please note that the I removed all of the dynamic date DAX formulation so that the visuals will be static and not change as time goes on, in order for referencing to images below to remain fixed.
I have also included pages with both old & new Matrix styles, to show that the issue occurs on both.
With “All” priorities selected in the slicer, all 3 tables display information correctly, and cards above display job count info
With priority filtered in slicer to “50”, cards above Matrix are now displaying a “(blank)” value which is correct. All 3 Matrices should be displaying no data, but continue to show same data as previous state.
With priority filtered in slicer to “85”, we can see that the yellow and green card/matrix visuals are displaying the correct priority 85 info, but the red matrix visual is still showing erroneous data (should be showing no data)
If you now page to the next page
And then page back again to the same page
We can now see that once the Matrix visuals have been repainted, the red card/matrix visual is now displaying the correct “no data” information
I have seen this issue reported at least twice elsewhere on these PBI forums, but nothing seems to have been done about it. I am hoping now that I have provided the supporting evidence of this fault, that Microsoft will address this issue a.s.a.p. as people within my organisation are reluctant to use a product that reports erroneous information.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.