In february we received an update that in some way improved new slicer but also broke it.
Quite a few people already wrote about it but nothing has happened over last half a year...
What's funny is that some topics have status ACCEPTER while other have INVESTIGATING
https://community.fabric.microsoft.com/t5/Issues/Cannot-set-fixed-number-of-rows-for-Slicer-New-visual-February/idi-p/3706216
https://community.fabric.microsoft.com/t5/Desktop/New-Button-Slicer-Layout-Feb-2024-Update/m-p/3714376
https://community.fabric.microsoft.com/t5/Issues/New-Button-slicer-visual-bug/idi-p/3717831
https://community.fabric.microsoft.com/t5/Issues/Glitches-in-New-Slicer-of-Power-BI-desktop/idi-p/4106937
So I decided to do a "small" summary
Before that update new slicer had only one layout option and it looked like this
Simple layout where you define fixed number of rows and columns (grid)
What february update brought us is 2 additional layout options (single column, single row)
The problem is visible on screenshots below
For every option ealier "Rows" was replaced with "Max buttons shown" or "Max rows shown"
While earlier "Rows" was a fixed number so even when we had less rows it was still displayed and aligned to "Rows" value, a fixed number (rows displayed = "Rows"). Now "Max buttons/rows shown" will adjust to the number of values in the slicer. If number of values is less than the "Max buttons/rows shown" buttons in slicer will change it's own size. Current situation can be described by a simple formula - rows displayed = MIN(number of values, max bottons/rows shown). And that is very problematic because it leads to situations like the one below
That second and third screenshot don't look too good... It would be much better if the buttons stayed the same height like in 1st picture.
I don't know if you noticed by now but some dev/team responsible for that change decided to keep "Columns" (just added "shown" for semantics) in Grid layout and it works like before, a fixed number of columns. So the only way to make it work like before that update is to display buttons horizontally but in 99.9% cases it's just bad.
Will this issue be resolved anytime soon? Just bring back old "Rows" functionality...
4 Comments
Hi IP_Kornel
So what does the desired outcome look like that you want to achieve? For example:
When you check one of these items, it shows up on the new slicer as normal size, rather than just taking up the whole interface, right ?
This happens when column show is set to 1. As shown in the picture column show is greater than 1, it will not take up the whole slicer as in your picture.
Column show value >1
If the column show is 1, and at the same time when you select an item in the slicer, the size of the item stays the same as before and doesn't fill up the whole slicer, is this result acceptable to you?
Best Regards,
Community Support Team _ Ailsa TaoHi Anonymous
The point is that if we filter this slicer by anything else, the button size shouldn't change no matter what.
The column part I mentioned earlier is to show how it should work for rows aswell. In grid layout there is no "Max" for "Colmns shown" same should be for rows in any layout option.
Who thought it would be a good idea for buttons to auto resize? Especially only for rows but not for columns???
You already new about it in february (over 6 months ago) and yet nothing was done so far
https://community.fabric.microsoft.com/t5/Issues/New-Button-slicer-visual-bug/idi-p/3717831Unfiltered default state:
Filtered (current):
What we want and what we used to have before february:Hi IP_Kornel
As you said, we submitted an ICM when this issue came up in Feb. According to PG's feedback, the issue has been identified as a design feature and is expected in the current version. The row count now becomes max row count and might change based on the amount of items. Designers will check if an option to keep the old behavior can be introduced .
You can vote the idea and comment there to improve this feature. It is a place for customers provide feedback about Microsoft Office products . What’s more, if a feedback is high voted there by other customers, it will be promising that Microsoft Product Team will take it into consideration when designing the next version in the future. Thank you for your cooperation!
Best Regards,
Community Support Team _ Ailsa Tao
