Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Slicer dropdown not showing data

Occasionally when I click the drop down arrow on my slicer, a small white box will appear where the drop down is supposed to be, but with no data displayed. I can fix the broken slicer by refreshing my browser page. This particular report has several slicers, and the issue can randomly occur on any of them with drop downs. This issue appears to only occur in Power BI Service, not Power BI Desktop. 

nkirse_0-1620764584595.png

 

Status: New
Comments
Pete_Swansea
Frequent Visitor

@TheoC I think you may be right with screen resolutions having an impact. I do not have 4K monitors, but have the issue on both of my 1080p monitors when the browser window fills the screen.

 

I have no issues when using my smaller laptop screen. 

 

Also if I shrink the browser window to less than full screen the slicers work, but the drop down options appear randomly elsewhere on the screen and not directly below the slicer itself.

TheoC
Super User

@Pete_Swansea it definitely is interesting!  Hopefully the Microsoft team will come up with a fix (if they haven't already... they're pretty quick to get on top of this to be honest).  

sydneycroud
Frequent Visitor

I believe you are right about the resolution. I had the same issue with a user and had him switch from a full screen in Microsoft Edge to the restored down setting, and the dropdown box worked normally. Oddly enough, if he was in Firefox, he didn't have this issue. I guess it's a Microsoft thing.

TheoC
Super User

@sydneycroud have you still been experiencing this issue?  Just out of curiousity, is your Microsoft web browser up-to-date?  I haven't experienced the issue for over a month now in any browswer but it is interesting it is still about (obviously, "interesting" not in a good way lol).

sydneycroud
Frequent Visitor

Yes, actually this was just reported last week, so was looking for the solution today when I stumbled on this thread. Our version is Version 93.0.961.52 (Official build) (64-b

I assume it's up to date as it's controlled by the organization. I'm just glad this fixed it.