Fields Parameter accepting incorrect input values during What-if Analysis

[Rajeshwar-s]

Hi everyone,

I've created a Fields Parameter (using Modeling > New Parameter > Fields) to generate a serial number with an incremental value of 1.

The auto created DAX is: = GENERATESERIES(500, 150000, 1)

This generates values like 500, 501, 502, …, 150000, and also checked for adding this parameter as a slicer for analysis.

However, I’m facing a strange issue when performing What-if Analysis — the slicer is accepting incorrect values.
For example:

• When I enter 1000, it changes to 948

• 700 becomes 649

• 1100 becomes 1097

• 1200 becomes 1247
  In this the snapshot see how the value is changing after entering

I’m unable to figure out whether I’ve made a mistake in setup or if this is a potential Power BI bug.

Has anyone else faced a similar issue or can suggest a workaround?

Thanks in advance!

[Shubham_rai955]

This issue happens because Power BI might not be handling the manual input values correctly in the slicer for What-if analysis.

Try these steps:
- Check your Power BI version and update to the latest one.
- Make sure the slicer uses the same number format as your parameter (like no currency or special symbols).
- Check your computer’s region and language settings for numbers and currency symbols.
- If it still doesn't work, it could be a bug in Power BI. You can report this to Microsoft or look for help in the Power BI community forums.

Hope this helps!

[v-achippa]

Hi @Rajeshwar-s,

Thank you for reaching out to Microsoft Fabric Community.

Thank you @danextian and @pbiuseruk for the prompt response.

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the user for the issue worked? or let us know if you need any further assistance.

Thanks and regards,

Anjan Kumar Chippa

[pbiuseruk]

I came up with a nice solution but it's not using parameters:

1. Generate a new table using the same dax query that you have. Go to the modelling tab and click on "New Table". Then just put in the generate series Dax that you have.

2. Make a slicer for the Value field (there'll only be 1 field)

3. In the slicer settings - make it greater than or equal to: 

4. Make a measure like this: 

Measure = min(table1[Value])

5. Make a data card and put in that measure

If you want, you can make a little white box and put it over the greyed out max part. But this should work in pretty much the same way as you want. Just reference this measure for any other things you want to calculate.

Please mark as the solution if this solved your query.

[pbiuseruk]

Use @danextian's solution below - I didn't realise you can just just change the slicer setting for the parameter. For you data cards or wherever you're referencing it - just make make sure you either use Min or Max before the parameter field value (depending on if you do "Less than or equal to" or "More than or equal to").

[danextian]

Hi @Rajeshwar-s 

This is a known issue with a single selection numeric parameter when there are many values to select from. Instead of single selection, use "Less than or equal to" and cover the grayed out area with a shape filled with a color that matches the background of the slicer.

[pbiuseruk]

Hello,

Have a look at Dans and DataNinjas comments in this thread: https://community.fabric.microsoft.com/t5/Desktop/What-if-parameter/m-p/4825064.

He mentions that there's a known limitation for large ranges and a workaround option to handle this.