Cannot set fixed number of rows for Slicer (New) visual - February 2024 Update

[khxlvin]

The functionality of the new slicer visual appears to be malfunctioning in the latest February 2024 update. The ability to set a fixed number of rows for display has been replaced with a maximum row setting which is not what we expect. The slicer will justify to the bottom if the number of rows is less than the maximum set in Format. This does not align to our current report specifications unfortunately. Is it possible to bring back the option to set a fixed number of rows instead of the maximum?

[v-xiaoyan-msft]

Hi @khxlvin ,

Since this is a new design update, I tested it separately on the last version and the latest February version .
It seems to look the same, could you show a gif or screenshot describing your issue, please be careful not to include sensitive information, thanks in advance!

2.124.2028.0 64-bit (December 2023)

2.126.927.0 64-bit (February 2024)

Best regards.
Community Support Team_Caitlyn

[khxlvin]

Hi @v-xiaoyan-msft,

Thank you for the reply. What I am referring is that the items are justified if the number of items in the slicer are less than the set maximum rows. Here, I set the maximum rows to 5 and columns to 1 but it is justified to the bottom.

2.126.927.0 64-bit (February 2024)

The last version does not justify the items of the slicer. This behavior aligns with our current requirements for our report but suddenly by the latest update, this is changed. As you may observe, the latest version changed the option to "Max rows shown" instead of just "Rows".

2.124.2028.0 64-bit (December 2023)

[memoX]

Hi @v-xiaoyan-msft @khxlvin 
I was going to submit same question. I have the same problem after FEB release.

My slicers look like magnified when it's filtered by another slicer, slicer button resizes itself to whole object size which doesn't make sense.

[v-xiaoyan-msft]

Hi @khxlvin ,

We have reported this issue and submitted it to the product team.
They have been aware of the issue and the engineers will do their best to resolve it. I will update here if there is any progress, so please be patient. 

Best regards.
Community Support Team_ Caitlyn

[IP_Kornel]

Hi,
was this solved in any way? It has been quite some time since "will do their best" and it's still a problem.

Version: 2.132.1053.0 64-bit (August 2024)