List Slicer in the service not maintaining layout settings from Desktop

[JustSayJoe]

Over the past few days all my List Slicers appear to be not maintaining the "buttons shown" layout when viewing them in the service. The example below is set to display 3 buttons, which is correctly shows in PBi Desktop, but when I publish up to the service you can see that it's unreadable due to the buttons shown layout not holding. I do have the "fixed number of buttons" option turned on in PBi desktop. Is there something else I might be missing, or is this just a Microsoft bug?

[v-tsaipranay]

Hi @JustSayJoe ,

Thank you for the update and hope this issue will be resolved in next update from microsoft.

[v-tsaipranay]

Hi @JustSayJoe ,

Could you please let us know if the issue has been resolved? If you still require support, please let us know, we are happy to assist you.

Thank you.

[JustSayJoe · Accepted solution]

@v-tsaipranay I spoke with someone at Microsoft Support about this, but the issue is not resolved, no. They told me it probably happened during the last update, and they couldn't tell me if/when it would be fixed because the developers don't give them timelines for bugs like this. They told me to just wait for the next PBi update to be pushed out and see if the bug gets fixed then, and in the meantime use a different slicer visual than the List Slicer.

[v-tsaipranay]

Hi @JustSayJoe ,

Thank you for confirming that you’ve submitted a support ticket. Based on the information and timing provided, it appears this may be a Service-side regression following the late September update.

Please share any updates from Microsoft here so others experiencing the same issue can stay informed. In the meantime, you can use the classic slicer as a temporary workaround until the problem is fixed.

Thank you.

[gabrifly]

Can confirm I have the same issue

[v-tsaipranay]

Hi @gabrifly ,

As IustSayJoe mentioned that after speaking with the Microsoft team, they informed him that the issue will be sorted in the next PBi update. hope that will be resolved in next update.

[somogyi23]

same issue here, since October 1.

[lbendlin]

Can you pinpoint the date when it started?

[JustSayJoe]

I cannot pinpoint the exact date or time, but I've noticed it only over the past 3 or so days if I had to guess.

[lbendlin]

You can mention the Sept 30 version change in the ticket.

[Greg_Deckler]

@JustSayJoe I would say to open a support ticket on that.

[JustSayJoe]

Thanks, I did just submit a ticket their way.