Almost every Power BI report ends up facing the same request: what if I wanted to see this by region instead of by product? Or: can you add margin here, next to revenue? The traditional answer was to duplicate visuals, fill the report with near-identical pages and hope nobody asked for one more variation.
Field parameters solve this problem elegantly. They let the person using the report choose, from a slicer, which metric or dimension they want to see — without the author having to build ten versions of the same chart. A single visual now answers many questions.
In this guide you will understand what field parameters are, how to create them step by step, where they make a difference and which traps to avoid. They are already a stable feature recommended for production, so you can use them in your reports with confidence.
What field parameters are and what problem they solve
A field parameter is a special table that Power BI creates to hold a set of fields — measures, columns or both — that the user can select in real time. By dragging that table into a slicer and into a visual, the chart stops being tied to a fixed metric or axis.
In practice, they turn a rigid report into a flexible one. Instead of one page for revenue, another for margin and another for units, you have a single page with a slicer that switches between the three. The same applies to dimensions: analysing by product, by region or by customer becomes one click.
How to create a field parameter step by step
The process is direct and does not require hand-written DAX:
- On the Modeling tab, choose New parameter and then Fields.
- Give the parameter a name — it will also be the name of the new table in your model.
- Drag into the left-hand box the fields you want to offer: measures such as revenue and margin, or columns such as product and region.
- Reorder the fields or double-click to change the display name the user will see.
- Confirm with Create. By default, Power BI adds a slicer to the canvas straight away and creates the parameter table in the model.
From here, drag the parameter field onto the axis or the values of a visual. The slicer controls what appears. Done.
Measures and dimensions in the same parameter
One of the most underrated capabilities is mixing types. Nothing stops a field parameter from containing, at the same time, measures (revenue, margin, number of orders) and columns (category, region). This opens the door to truly dynamic visuals, where the user chooses both what to measure and how to break it down.
Some common sense is required: not every combination makes sense, and a slicer with thirty options confuses more than it helps. Flexibility is a tool, not a goal.
Use cases where they make a difference
- Dynamic axis: a single bar chart the user views by product, by region or by month, depending on their choice.
- Dynamic metric: a card or a time series that switches between revenue, margin and units.
- One report for several teams: instead of versions per department, each person selects the indicators that matter to them.
- Fewer pages, less maintenance: consolidating five near-identical pages into one reduces the effort of keeping everything aligned.
Short case: a management control team
The management control team of an industrial company kept a monthly report with one page per metric and per dimension: revenue by product, revenue by region, margin by product, margin by region, and so on. In total, twelve near-identical pages that had to be formatted and checked one by one at every close.
With field parameters, they collapsed everything into three pages: one for evolution, one for comparison and one for detail, each with two slicers — one for the metric, one for the dimension. The monthly maintenance time for the report dropped from about a full day of work to less than two hours. And, perhaps more importantly, the number of active users rose by around 40%, because each manager could now answer their own questions without asking for a new version.
The path was not immediate: the team had to re-educate users, used to looking for the margin page. A small help section at the top of the report resolved most of the questions.
Field parameters or bookmarks: which to choose
Before field parameters, the usual way to offer alternative views was with bookmarks and buttons: create several stacked visuals and toggle their visibility. It works, but it is fragile — every new metric means one more visual, one more bookmark and one more button, and maintenance grows quickly. Field parameters do the same job with a single table and a slicer, and they scale much better as the options grow. Bookmarks remain useful for changing the layout or telling a guided story; field parameters are the right choice when what changes is the field under analysis.
Dynamic title: making the visual follow the choice
A dynamic report without a dynamic title is a trap: the chart changes, but the header still says Revenue when the user is already looking at Margin. The fix is a simple measure that returns the name of the selected field and serves as the visual's title:
Title = SELECTEDVALUE(Parameter[Name], "Overview")
The second argument sets the text to show when several options are selected at once. With this detail, the visual explains itself and the user is never in doubt about what they are seeing.
Limitations and things to watch
Field parameters are not the answer to everything, and it is worth knowing the limits:
- Do not confuse field parameters with What-if parameters, which are meant to simulate numeric values, not to swap fields.
- The formatting of each measure can vary (percentages, currency, integers); a dynamic visual does not always apply the ideal format to every option.
- Some interactions — such as certain types of drill or conditional formatting that depends on a specific measure — can behave unexpectedly when the field is dynamic.
- A slicer with too many options hurts the experience; group and limit it to what is useful.
Common mistakes
- Stuffing the parameter with fields: more options is not a better report. Choose the ones that answer real questions.
- Forgetting the dynamic title: if the visual changes metric, the title should change with it, or the user gets lost. A measure with
SELECTEDVALUEsolves this. - Not testing the formatting: check how each option looks before publishing, especially when mixing currency and percentage.
- Assuming everyone gets it: a dynamic report is powerful but less intuitive; a help note makes a difference.
Best practices
Use clear names for the parameter fields — that is what the user sees. Create a dynamic title with SELECTEDVALUE so the visual reflects the choice. Keep each parameter focused on one purpose (one for metrics, another for dimensions, rather than a single huge one). And document, even in a discreet text box, what the slicers do.
In practice
Field parameters are one of those features that look small and change how you build reports. Instead of answering every new request with one more page, you hand the user the keys to explore on their own. The result is leaner reports, easier to maintain and, almost always, more used. Start with a report where you have repeated pages — that is where the gain is immediate.
