Matrix Visual doesn't work with Field Parameters (on rows) in Version: 2.145.631.0 (July, 2025)

[modi123p]

Hi,

Note: Issue noticed in unreleased July 2025 edition of PBI Desktop.

I m using Field Parameters on Rows of the Matrix and trying to provide dynamic selection for the users.

However, the functionality stops after making slicer selection a couple of times and

expand/ drill down buttons no longer works.

For the selection as shown in snapshot below, I would expect the user to expand and see Col2 and Col3 in the matrix visual. However.  no matter how many times you click, its not possible to expand. It is not dependent on the order of selection of columns or layout configuration in use. Request you to address the issue ASAP.

Sample PBIX is available at the below link:

Test/Test Matrix.pbix at main · modi123p/Test

Thanks & Regards,

Madan Prabhakara

[DeeceC]

Yes this is now evident in the service, all our matrix visuals with field aprams are broken. This used to work prior to last service update.

However it is working in June desktop version  2.144.1378.0 64-bit (June 2025) however currently broken in service

[mtrando]

My users are having the same issue

[Rom_Cheng]

Have the same issue and don't find any workaround yet.

[adam_hfg]

Same issue here, impacting 1/3 of my active users.

[zsombor]

I have an issue with the expand/collapse functionality on the rows when I use the +/- or the context menu. With multiple parameters in the filter, it does not work. Without any filter condition seems to work. I have the same issue in the service and in the desktop app as well. It is affecting 50+ users on my side.

[levkro1234]

We are experiencing a similar issue on our side: the expand/collapse functionality fails to work properly when multiple filter parameters are applied. This affects the majority of our reports and significantly impacts usability. It worked normally during the demo mode but broke after switching to the main feature. It works as expected only when no filter conditions are set, which clearly suggests it's a bug. We hope this will be addressed and resolved soon.