Don't miss your chance to take exam DP-600 or DP-700 on us!
Request nowLearn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
Starting with the January 2026 version of Power BI, we can turn off the "Persist hierarchy level" feature.
Only work with the default parameter column.
This works when we use the default parameter column information, but not if we use grouped information from the field parameter. For example, I created group1 and group2.
Field parameter
Data table
It works with the default field column. See the first image below.
It works with the default field column.
Using the value4 column from the Field Parameter doesn't work!
It doesn't work if I select group2 first, followed by group1.
The table needs to show region (North or South) as the first level and country as the second level.
It doesn t work
Do you have any ideas about how to work with the value4 column?
Solved! Go to Solution.
Hi @Josemar_23 ,
I believe you are mixing up two different things.
The only columns that will change dynamically the values on the visualizations is the column Parameter Fields, because this column is where the engine recognizes that you want to use a specific field or measure that is because of the NAMEOF syntax. Other columns that you add to your parameter table, in this case value4, are only categorization of the fields this allows you to have different aggregations of your data and filtering of the columns they will not allow you to have the selected columns in the visual.
The second concept is the "Persist Hierarchy Level" that allows you to keep your data expanded when you change field parameters on your visualization using the slicers having this option on will keep the matrix close or open.
In this case if you want to have a change between column so having region/country or country/region you would need to extend your field parameter like this:
Parameter = { ("Column1", NAMEOF('Table'[Column1]), 0,"group1"), ("Column2", NAMEOF('Table'[Column2]), 1,"group1"), ("Column1", NAMEOF('Table'[Column1]), 3,"group2"), ("Column2", NAMEOF('Table'[Column2]), 2,"group2") }
Now using slicer for group you can have it change the hierarcy.
Regards
Miguel Félix
Proud to be a Super User!
Check out my blog: Power BI em PortuguêsHi @Josemar_23 ,
I believe you are mixing up two different things.
The only columns that will change dynamically the values on the visualizations is the column Parameter Fields, because this column is where the engine recognizes that you want to use a specific field or measure that is because of the NAMEOF syntax. Other columns that you add to your parameter table, in this case value4, are only categorization of the fields this allows you to have different aggregations of your data and filtering of the columns they will not allow you to have the selected columns in the visual.
The second concept is the "Persist Hierarchy Level" that allows you to keep your data expanded when you change field parameters on your visualization using the slicers having this option on will keep the matrix close or open.
In this case if you want to have a change between column so having region/country or country/region you would need to extend your field parameter like this:
Parameter = { ("Column1", NAMEOF('Table'[Column1]), 0,"group1"), ("Column2", NAMEOF('Table'[Column2]), 1,"group1"), ("Column1", NAMEOF('Table'[Column1]), 3,"group2"), ("Column2", NAMEOF('Table'[Column2]), 2,"group2") }
Now using slicer for group you can have it change the hierarcy.
Regards
Miguel Félix
Proud to be a Super User!
Check out my blog: Power BI em PortuguêsShare feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 51 | |
| 40 | |
| 37 | |
| 14 | |
| 14 |
| User | Count |
|---|---|
| 85 | |
| 69 | |
| 38 | |
| 29 | |
| 27 |