Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
Skater
Regular Visitor

Scenario mapping table

I need help getting a scenario mapping table to work with with a slicer. For example, scenario 1 should use all the parameters on that row. One of the parameters refers to say a list of accounts from the chart of accounts. The specific scenario 1 chart of accounts is slicer wher the user can select the accounts within that scenario 1 to impact with the other parameters with that scenario say start date and percentage increase all users selectinons for parameter 1 group. My issue is that there the chart of accounts is in the slicer but the scenario table only refer to the table name that contains the chart of account table. I've set separate tables for the parameter percentage, start year and chart of accounts single column which I'm using all as single select slicers except for the chart of accounts as a multi select. Any suggestions?

4 REPLIES 4
Skater
Regular Visitor

Thanks a I'll work through a solution and let you know how it goes.

wardy912
Impactful Individual
Impactful Individual

Hi @Skater 

 

 Use a field parameter, really straight forward to set up and will solve your issue.

 

From the modeling tab, select 'new parameter' then 'fields'

 

wardy912_0-1755867972987.png

 

You can choose any column from any table in the next section, I tend to use this to slice between calendar/fiscal calendar dates. Keep 'Add slicer' ticked to automatically add your slicer

 

wardy912_1-1755868218387.png

This will create a table, select your parameter from that table and add to your visual

wardy912_2-1755868334550.png

I hope this helps, please mark as solved if it does, thanks!

 

 

 

Thanks a I'll work through a solution and let you know how it goes.

Mvsainathareddy
Advocate II
Advocate II

Hi @Skater 

Yes, you can use Field Parameters in Power BI to help manage dynamic slicer behavior — especially when you want users to switch between different dimensions or measures in visuals. However, for your scenario mapping use case
Let’s break it down:
What Field Parameters Can Do
Field Parameters allow users to:
- Dynamically switch between columns or measures in visuals.
- Create slicers that control which fields are displayed.
How Field Parameters Might Help in Your Scenario
If your goal is to let users switch between different parameter groups (e.g., start year, percentage increase, chart of accounts), Field Parameters can help by:
- Creating a slicer that lets users choose which parameter to apply.
- Dynamically updating visuals based on the selected parameter.

But Field Parameters don’t inherently filter data — they control what is shown , not how it’s filtered .
Recommended Hybrid Approach
To make your scenario mapping work with slicers and Field Parameters:

1. Create a Scenario Mapping Table
Include:
- Scenario Name
- Start Year
- % Increase
- Account ID

2. Relate Account ID to Chart of Accounts Table

3. Use Field Parameters for Visual Switching
Create a Field Parameter table like:

DAX
FieldParameter = {
("Start Year", NAMEOF('ScenarioMapping'[Start Year])),
("% Increase", NAMEOF('ScenarioMapping'[% Increase])),
("Account", NAMEOF('ScenarioMapping'[Account ID]))
}

This lets users switch between parameters in visuals.

4. Use Slicers for Filtering
- Scenario slicer filters the scenario mapping table.
- Chart of accounts slicer filters the account table, which is linked to scenario mapping.

Helpful resources

Announcements
August Power BI Update Carousel

Power BI Monthly Update - August 2025

Check out the August 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.