The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends September 15. Request your voucher.
Hi,
I have a problem with the field parameters. Before the july update, I was able to inverse a hierarchy of two dimensions in a matrix by doubling the lines in the parameters table and add a fourth column who group the different choice for the users. My table look like this :
Region - Column Region - 0 - Region
Sector - Column Sector - 1 - Region
Sector - Column Sector - 2 - Sector
Region - Column Region - 3 - Sector
Then, you put the parameters in the matrix and the fourth column in a slicer. It was perfect before the update.
So, do you think it's a bug that microsoft will fix short-term? Because my report rely heavily on this functionnality! Or do you think it was intentional to remove this functionnality?
Thank you and have a good day!
Solved! Go to Solution.
Hi @WilliamBalleux,
Thank you for your follow-up question. I’m happy to explain how to replicate the hierarchy switching feature with a manual slicer table and DAX logic, especially since Field Parameters now work differently after the July update.
To start, you’ll need to create a manual slicer table that lets users select their preferred hierarchy option.
HierarchyOptions =
DATATABLE(
"Option", STRING,
{
{"Region > Sector"},
{"Sector > Region"}
}
)
Add this table to your data model and set up a slicer using the Option column.
Next, create conditional DAX measures that switch the hierarchy dynamically based on the slicer selection.
SelectedOption = SELECTEDVALUE(HierarchyOptions[Option])
RegionDisplay =
IF(
SelectedOption = "Region > Sector",
SalesData[Region],
SalesData[Sector]
)
SectorDisplay =
IF(
SelectedOption = "Region > Sector",
SalesData[Sector],
SalesData[Region]
)
These calculated columns or measures will serve as dynamic fields within your matrix visual.
Thank you.
Hi
Thank you @danextian for sharing the link to the query and Thank you @WilliamBalleux for reaching out and sharing detailed information about the field parameter behavior in the matrix visual following the July update. We recognize the importance of this functionality for your reporting requirements.
We can confirm that the July 2025 update introduced a change affecting Field Parameters in matrix visuals, particularly in cases where parameter tables included duplicate entries to enable hierarchy inversion.
This is a known issue, and our internal teams are currently investigating it. Other users have also reported the behavior you described, where the matrix no longer applies the manual inversion setup using duplicated entries and slicer grouping.
Until an official fix becomes available, we recommend considering one of the following options:
Revert to a previous version of Power BI Desktop (June 2025 or earlier), provided this is allowed by your organization.
Create a manual slicer table outside of field parameters and apply conditional logic in your DAX to display the appropriate hierarchy as needed.
Utilize two separate visuals, using a slicer or bookmark workaround to toggle visibility, with each visual configured for a specific hierarchy version.
Thank you.
Hi,
Thank you for the reply. Is it possible de developp this solution : Create a manual slicer table outside of field parameters and apply conditional logic in your DAX to display the appropriate hierarchy as needed.
How to set this up?
Thank you and have a good day!
Hi @WilliamBalleux,
Thank you for your follow-up question. I’m happy to explain how to replicate the hierarchy switching feature with a manual slicer table and DAX logic, especially since Field Parameters now work differently after the July update.
To start, you’ll need to create a manual slicer table that lets users select their preferred hierarchy option.
HierarchyOptions =
DATATABLE(
"Option", STRING,
{
{"Region > Sector"},
{"Sector > Region"}
}
)
Add this table to your data model and set up a slicer using the Option column.
Next, create conditional DAX measures that switch the hierarchy dynamically based on the slicer selection.
SelectedOption = SELECTEDVALUE(HierarchyOptions[Option])
RegionDisplay =
IF(
SelectedOption = "Region > Sector",
SalesData[Region],
SalesData[Sector]
)
SectorDisplay =
IF(
SelectedOption = "Region > Sector",
SalesData[Sector],
SalesData[Region]
)
These calculated columns or measures will serve as dynamic fields within your matrix visual.
Thank you.
Hi @WilliamBalleux,
I wanted to check in your situation regarding the issue. Have you resolved it? Should you have any further questions, feel free to reach out.
Thank you for being a part of the Microsoft Fabric Community Forum
Hi @WilliamBalleux,
We wanted to follow up since we haven't heard back from you regarding our last response. We hope your issue has been resolved.
If you need any further assistance, feel free to reach out.
Thank you for being a valued member of the Microsoft Fabric Community Forum!
Hi @WilliamBalleux,
As we have not received a response from you yet, I would like to confirm whether you have successfully resolved the issue or if you require further assistance.
Thank you.
Hi,
I haven't had time to test your solution yet. I'll try it at the end of the week.
Thank you!
Hi @WilliamBalleux,
Thank you for the update.
Please take your time, and let us know when you are able to test the solution. We are available to provide any additional assistance you may need.
Continue using Microsoft Fabric Community Forum.
Might be related to this: https://community.fabric.microsoft.com/t5/Issues/Matrix-Visual-doesn-t-work-with-Field-Parameters-on...
User | Count |
---|---|
65 | |
62 | |
60 | |
53 | |
30 |
User | Count |
---|---|
181 | |
83 | |
68 | |
49 | |
46 |