Decimal level parameter not working

[Pra2010Gha]

Hello I am trying to pass value to a decimal parameter say 45.67 but it is rounding up to some wierd number.I want it to show the entered value as it is

like if i enter 45.67 it will show 45.94

for 38.54 it will show 38.96..Any help is appreciated

[Pra2010Gha]

hello, so I tried doing some adjustments here ..I am able to get the parameter decimal value but I want the search function in numeric range

[v-achippa]

Hi @Pra2010Gha,

The numeric range parameter or slicer in power bi does not support a search box, it only allows selecting or typing a range of numeric values.

If you need a search option, then create a text version of your numeric values and use that in a dropdown slicer instead, for example like below:

ValueText = FORMAT(YourTableName[ParameterValue], "0.00")

Then add a slicer using ValueText and it will automatically show a search box where you can type numbers like 45.67.

Thanks and regards,

Anjan Kumar Chippa

[v-achippa]

Hi @Pra2010Gha,

We wanted to kindly follow up to check if the solution I have provided for the issue worked? or let us know if you need any further assistance.

Thanks and regards,

Anjan Kumar Chippa

[ANVS]

Hello @Pra2010Gha

I suggest these 2 options for the workaround:


Option 1: Increase Increment Precision

Try setting the Increment value to 0.001 or even smaller (like 0.0001).
This makes Power BI’s internal floating math more stable and keeps entered values closer to what you expect.

Steps:

1. Go to Modeling → New Parameter → Numeric Range

2. Set:

   • Data type: Decimal number

   • Minimum: 0

   • Maximum: 1000

   • Increment: 0.001

   • Default: 0 (or your desired default)

This reduces the rounding error.

Option 2: Round the parameter value in a measure

If you already created the parameter and can’t change it, use ROUND() in your DAX expressions to fix the visible issue.

Example DAX:

Adjusted Parameter =
ROUND( 'Parameter'[Parameter Value], 2 )

Then use the Adjusted Paramter Measure wherever you previously used the parameter.

[gmsamborn]

Hi @Pra2010Gha 

I'm not sure but I think the problem might have to do with the number of discrete values in your slicer.

I've run into this in the past and it appears you want to have 100,000 discrete numbers in the slicer.   

I can't remember the actual number but different visuals (including slicers) have actual limits, and that once that limit is broken, sampling occurs.

Once sampling occurs, it would look exactly like what you are seeing.

I wish I still had the link.

Hopefully this helps.  (Maybe AI could help with the limits for the relevant visuals.)

[Pra2010Gha]

What link are you talking about?How did you manage?

[lsilvestre]

Same problem here. I'm trying to set the slicer state with decimal numbers #.00, and facing the same problem

[marcelsmaglhaes]

Hey @Pra2010Gha 

It sounds like Power BI is misinterpreting the decimal values due to regional settings. For example, when you enter 45.67 and it shows 45.94, it's likely treating the input incorrectly because of the decimal separator.

Since your increment is set to .01, make sure you're entering numbers using a dot (.) as the decimal separator, like 1000.00 instead of 1000. Also, double-check that your regional settings are setting correctly, so Power BI interprets the values as expected.

Try that and let me know if works. 

Edited: If didn't work, try look at Solved: Parameter (decimal) resolving to incorrect value - Microsoft Fabric Community

[Pra2010Gha]

so what should be the regional settings to interpret it correctly?

Also, I am entering the value with decimal seperator like 45.67 and not 45

[v-achippa]

Hi @Pra2010Gha,

Thank you for reaching out to Microsoft Fabric Community.

Thank you @marcelsmaglhaesand @gmsamborn for the prompt response.

This issue happens because the parameter or slicer is trying to handle too many discrete numeric values. When the range is large and the increment is very small like for example 0 -1000 with a 0.01 step, power bi automatically samples or like snaps the available values into a smaller set of ticks. That causes the entered decimal to round to the nearest tick, which is why a value like 45.67 shows as 45.94.

• Increase the increment for example like to 0.1 or reduce the range so that there are fewer discrete values.

Thanks and regards,

Anjan Kumar Chippa

[v-achippa]

Hi @Pra2010Gha,

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

Thanks and regards,

Anjan Kumar Chippa