How to Create Nested Field Parameters in Power BI Matrix (Show Columns Dynamically Based on Slicer)

hi Mahendra_k ,

this is a fairly advanced Power BI modeling pattern. Let's discuss how you can implement nested field parameters (Old vs New + Dynamic column selection) step-by-step 👇

🎯 Goal

• You already have a Field Parameter that dynamically controls columns in a Matrix.
  Now you want a second slicer (Old/New) that toggles between “Old City” and “New City” without breaking the main parameter’s functionality.
  
  

🧩 Steps

1. Create a City Version Table

Create a small disconnected table for the Old/New toggle:

CityVersion =
DATATABLE(
    "City Version", STRING,
    {
        {"Old"},
        {"New"}
    }
)

This will drive your “Old/New” slicer.

2. Create Two Measures for City Columns

Instead of directly using the columns (Old City, New City) in your field parameter, create measures that switch based on slicer selection.

Example:

Selected City =
VAR sel =
    SELECTEDVALUE('CityVersion'[City Version])
RETURN
    SWITCH(
        TRUE(),
        sel = "Old", MAX('YourTable'[Old City]),
        sel = "New", MAX('YourTable'[New City]),
        BLANK()
    )

This measure dynamically shows either Old or New City based on slicer selection.

3. Update Your Field Parameter

Open your existing Field Parameter table (it might look like this):

ColumnParameter =
{
    ("Sales", NAMEOF('YourTable'[Sales]), 0),
    ("Profit", NAMEOF('YourTable'[Profit]), 1),
    ("Old City", NAMEOF('YourTable'[Old City]), 2),
    ("New City", NAMEOF('YourTable'[New City]), 3)
}

➡ Replace the two city entries with your [Selected City] measure instead:

ColumnParameter =
{
    ("Sales", NAMEOF('YourTable'[Sales]), 0),
    ("Profit", NAMEOF('YourTable'[Profit]), 1),
    ("City", NAMEOF([Selected City]), 2)
}

4. Build Your Visual

1. Add a Matrix visual.

2. Place the Field Parameter slicer (from your original parameter table).

3. Add the CityVersion slicer (Old/New).

4. Use the parameter field in your Matrix columns — it will now dynamically switch both:

   • Columns shown (via parameter slicer),

   • Old/New City (via CityVersion slicer).

5. (Optional) Improve Usability

• Rename [Selected City] to “City (Dynamic)” for clarity.

• In the slicer, set single select for CityVersion (to avoid conflicts).

• You can add conditional formatting or tooltips to show which version is currently active.

⚙️ Working

• The Field Parameter controls which fields/measures appear in the matrix.

• The CityVersion slicer drives a measure that acts as a proxy for both city columns.

• Because Field Parameters can include measures, this pattern allows you to “nest” dynamic logic inside them.
  
  

🧠 Key Insight

Power BI doesn’t yet support true nested field parameters, but you can simulate them by:
Replacing any column with a measure that responds to another slicer (as shown above).

This technique is widely used for “Old vs New”, “YTD vs MTD”, or “Current vs Previous” dynamic views.


⭐Hope this solution helps you make the most of Power BI! If it did, click 'Mark as Solution' to help others find the right answers.
💡Found it helpful? Show some love with kudos 👍 as your support keeps our community thriving!
🚀Let’s keep building smarter, data-driven solutions together!🚀 [Explore More]

Hi Mahendra_k 
download the attachment and see if it is what you need.
Mark as a solution if it help you.

Hi Mahendra_k, if I understood your request correctly you just need to add additional columns to your Field Parameter:

To do so you just have to add a comma at the end of each row in the Field Parameter definition before the closing bracket and type whatever category you want to assign it to. You can add as many columns as you need like this to create a hierarchy. The important note is just that all rows need to have the same amount of columns at the end. 

Hi Mahendra_k 

You can actually create a conditional calculated column in the field parameters table. You should able to use this calc column in a slicer. Note: this column cannot be used to create a hierachy in any other visuals.

Hi Mahendra_k 

Yes, this can be done, but not with a single native field parameter, since Power BI currently doesn’t support nested or conditional field parameters out of the box. However, you can achieve the desired behavior by combining your existing field parameter with a supporting DAX measure or by creating a secondary parameter table to control the Old vs. New column dynamically. The idea is to have your original field parameter continue managing the selection and arrangement of the majority of columns, while introducing a second slicer that determines whether the “City” column in the matrix represents Old City or New City.

One clean way to do this is to replace the Old City and New City fields in the parameter with a single “City” placeholder, and then use a DAX measure (or calculated column) that switches between Old City and New City values based on the slicer selection. For example, you can create a disconnected table with two rows: “Old” and “New,” use it as a slicer, and then define a DAX measure like:

Selected City =
VAR _sel = SELECTEDVALUE(CityToggle[Type])
RETURN
    SWITCH(
        _sel,
        "Old", SELECTEDVALUE(Table[Old City]),
        "New", SELECTEDVALUE(Table[New City])
    )

Then, in your field parameter table, remove the original Old City and New City fields, and add this new Selected City measure as one of the parameter fields. This way, when users toggle between Old and New, the “City” column in the matrix dynamically reflects the correct field, while the existing field parameter slicer continues to control the visibility and order of other columns independently.

Alternatively, if you want more flexibility, you could use two field parameter tables — one for the version selection and one for the general columns — and then use a matrix with measures or a composite field parameter (by UNION-ing the parameter tables) to combine both behaviors, though that’s more advanced and harder to maintain. The first approach — using a toggle slicer plus a DAX measure in the parameter — is generally the simplest and most robust way to achieve this nested control.