Field parameters (Power BI)

What are field parameters?

Field parameters are a Power BI feature that lets the people reading a report choose which fields or measures a visual shows, by clicking a slicer. One bar chart can flip between sales, profit and quantity, or switch its axis between product, region and customer, without you building three separate charts.

The point is self-service. Instead of the report author deciding every view in advance, the reader steers the analysis themselves, and the page stays tidy because a single visual covers what used to need several.

How you create one

You build a field parameter from the Modeling tab: New parameter, then Fields. You give it a name and pick the fields and measures to include, and you can drag to reorder them or rename how each one appears. Power BI then adds a slicer to the page automatically, wired to the parameter, so the reader can select an option straight away.

You can mix measures and dimensions in the same parameter. To make a chart fully steerable, put a field parameter of measures in the value well and a field parameter of dimensions on the axis; the reader then controls both what is measured and how it is grouped.

What Power BI builds behind the scenes

A field parameter is a small calculated table in your semantic model. Power BI writes it for you using the NAMEOF function, which returns the name of a measure or column as text. Each row pairs a display label, a reference to the real field, and a sort order.

Metric = {
    ("Sales", NAMEOF('Sales'[Total Sales]), 0),
    ("Profit", NAMEOF('Sales'[Total Profit]), 1),
    ("Quantity", NAMEOF('Sales'[Order Quantity]), 2)
}

When the reader picks a row in the slicer, the visual resolves the stored reference and swaps in that field. Seeing the table for what it is helps explain the limits below: it is model metadata, not magic, so anything that cannot be expressed as a named field reference does not fit.

Common use cases

• One chart, many metrics. Let a reader view the same trend as revenue, margin or units sold from a single slicer, instead of scrolling past three near-identical charts.

• Switchable grouping. Keep one chart and let the reader break it down by product, region, channel or month, whichever they need at that moment.

• Cleaner pages. Collapse a wall of visuals into a couple of steerable ones, which is easier to maintain and lighter to load.

• Personal exploration. Give business users room to answer their own follow-up questions without asking for a new report each time.

What to watch out for with field parameters

• Only explicit measures work. You cannot use an implicit measure, so if you want to switch to an aggregated column, write a real DAX measure for it first.

• No way to select nothing. There is no "none" option; if a reader selects no field in the slicer, Power BI treats it the same as selecting all of them.

• Not everything supports them. AI visuals and Q&A do not work with field parameters, and you cannot use a field parameter as the linked field of a drill-through or tooltip page. The workaround for drill-through is to link the individual fields the parameter contains.

• You need a local model. Field parameters cannot be created on a live connection without a local model, so a pure live connection to a semantic model or Analysis Services needs a composite model on top before you can add one.