Power BI Field Parameters: Dynamic Reports Made Easy

A common report pattern is several nearly identical charts: sales by country, sales by product, profit by country, profit by product. Each one takes space, and readers scroll to find the combination they want. Field parameters replace them with one visual and a slicer. Microsoft's description is simple: they let report readers dynamically change the measures or dimensions they are analysing, by selecting from a slicer (Microsoft Learn: field parameters).

Creating a field parameter

1. On the Modeling tab in Power BI Desktop, select New parameter, then Fields.
2. Name the parameter and select the fields it should offer, for example Country, Segment and Product for a "Group by" parameter, or the Sales, Profit and Units measures for a "Measure" parameter.
3. Drag to reorder the fields, and double-click one to change its display name.
4. Add the parameter to a slicer, so readers have a control for choosing fields.

You can mix measures and dimensions in one parameter, which is useful for a table whose columns readers choose themselves.

Using it in visuals and slicers

Put a column-based parameter in a visual's axis or rows, and a measure-based parameter in its values. When a reader selects a field in the slicer, every visual bound to the parameter switches to it. If the visual supports several measures and the reader selects more than one, they appear side by side.

Slicers can display a parameter in two ways. By default they show the field names, so readers choose which field to use. For parameters made of columns, you can instead right-click the parameter in the Build pane and choose Show values of the selected field, which turns the slicer into a hierarchy slicer listing the values of each field. Microsoft suggests this for fields that form a natural hierarchy, such as year, month and day of the week, so readers can filter at any level from one slicer.

What the parameter really is

Behind the dialog, a field parameter is a calculated table defined in DAX. Each row has three values: a display name, a reference to the field made with NAMEOF, and an order number:

Group by = {
    ("Country", NAMEOF ( 'Customer'[Country] ), 0),
    ("Segment", NAMEOF ( 'Customer'[Segment] ), 1),
    ("Product", NAMEOF ( 'Product'[Product] ), 2)
}

NAMEOF returns the name of a column or measure as text, fully qualified by default (DAX reference: NAMEOF). Because it refers to the object rather than to a typed string, a renamed column or measure keeps working in the parameter. You can edit this expression to add, rename or reorder fields. Microsoft warns against adding extra columns: define exactly three values per field, and keep the values unique, or results can be unexpected.

Dynamic titles

A chart whose content changes needs a title that changes with it. A measure that reads the selected display names can feed the visual's title through conditional formatting:

Chart Title =
"Selected measure by " & SELECTEDVALUE ( 'Group by'[Group by], "several fields" )

The first column of the parameter table, named after the parameter, holds the display names. Without a dynamic title, readers can lose track of what the chart currently shows.

Matrices and hierarchy levels

When a matrix uses a field parameter alongside another field, such as a Product Group parameter with Year on rows, changing the parameter can keep or collapse the expanded levels. The Persist hierarchy level setting, in the report settings under field parameters, controls this: on, the matrix stays expanded when readers switch fields; off, it collapses.

Limitations to know before you build

Microsoft lists several:

• No implicit measures. An aggregated column must be an explicit DAX measure before it can be offered.
• No "none" option. Selecting no fields behaves the same as selecting all of them.
• AI visuals and Q&A are not supported with field parameters.
• Not for drillthrough or tooltip pages. Link those pages to the individual fields that the parameter references instead.
• Date hierarchies are lost when an auto date/time column is used; add Year, Quarter, Month and Day as separate fields if you need them.
• Live connections need a local model: parameters cannot be created on a live connection without one.

Field order in a visual also follows the order readers select fields in, unless a hierarchy slicer sets it.

Field parameters, bookmarks or calculation groups?

• Field parameters switch which fields a visual uses: a different measure or a different grouping. Filters and interactions keep working.
• Bookmarks switch between different visuals or page states, such as a chart and a table; bookmarks and buttons covers them. For "same chart, different measure", field parameters are simpler to maintain.
• Calculation groups apply the same calculation, such as year to date or prior year, to whichever measure is shown; calculation groups covers them. They combine well with field parameters: one chooses the measure, the other the time calculation.

Design advice

• Offer a short list. Three to six fields per parameter keeps choices meaningful.
• Use button slicers for small parameters, so options are visible without opening a menu.
• Keep formats compatible. Switching between a currency measure and a percentage on the same axis can confuse; group measures of the same kind.
• Set a sensible default by saving the report with the most useful selection.

Power BI dashboard design covers how dynamic visuals fit into a well-structured page.

Parameters and dynamic reports are part of the advanced Power BI module of the Power BI course.

Sources

• Use field parameters in Power BI reports (Microsoft Learn) — Microsoft Learn
• NAMEOF function (DAX reference, Microsoft Learn) — Microsoft Learn