Power BI

How to Create a Custom Numeric Range Slicer With Parameter in Power BI Easily 2026

By Impran M N

Power BI's default numeric slicer works fine for simple filtering, but a parameter-based range slicer gives you more control over how viewers narrow down numeric data like revenue bands or age ranges. This guide covers setting up your data model, building the parameter, and wiring it into a working slicer. It's aimed at report builders who need more flexible numeric filtering than the out-of-the-box option provides.

01Set up your data model

Confirm the numeric field you want to filter is clean and available in your model, since the parameter will reference its range of values.

02Create the numeric range slicer

Use Power BI's What-If Parameter feature to define a numeric range with a minimum, maximum, and increment step that matches your data.

03Implement the parameter in your report

Connect the resulting parameter slicer to a measure that filters your visuals based on the selected range, using DAX to compare values against the parameter.

04Explore practical use cases

Use this technique for scenarios like filtering customers by revenue range or products by price band, where a simple min-max slicer isn't flexible enough.

FAQ

Frequently asked questions

How is a parameter-based slicer different from Power BI's built-in numeric slicer?

A parameter-based slicer gives you more control over step increments and lets you tie the selected range into custom DAX logic, rather than relying on the default between-style slicer.

Do I need DAX knowledge to build this kind of slicer?

Basic DAX helps, since you'll typically write a measure that compares your data against the selected parameter value to drive the filtering.

Can I use a numeric range slicer for filtering dates or IDs too?

It's designed for continuous numeric values like revenue or age, and while it can technically filter numeric IDs, it works best for values where a range genuinely makes sense.

Will this slicer update automatically as new data comes in?

Yes, as long as the underlying field and DAX measure reference the live data model, the slicer's filtering logic applies to new records automatically after a refresh.