Parameter (decimal) resolving to incorrect value

[jmont031]

Hi all

So, my problem is that my parameter is resolving to a value different than that entered.

parameter is GENERATESERIES(0, 1, 0.0001)

When I enter 0.0714 (7.14%) it resolves to 0.0709 (7.09%) I have attached images. 0.0715 becomes 0.0719. 0.182 becomes 0.1818.

This is in a single value parameter. If I have a between/range parameter (image) it returns the typed value i.e. 7.14%.

Any help would be very much appreciated

[v-echaithra]

Hi @jmont031 ,

If the provided answer was helpful, please mark it as "Accept as solution" and click "Yes" if you found it helpful, it will be helpful for other members of the community who have similar problems as yours to solve it faster.

Regards,
Chaithra.

[v-echaithra]

Hi @jmont031 ,

May I ask if you have gotten this issue resolved?

If it is solved, please mark the helpful reply or share your solution and accept it as solution, it will be helpful for other members of the community who have similar problems as yours to solve it faster.

Regards,
Chaithra.

[v-echaithra]

Hi @jmont031 ,

We would like to follow up to see if the solution provided by the user resolved your issue. Please let us know if you need any further assistance.
If the provided response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.

Regards,
Chaithra.

[burakkaragoz]

Hi @jmont031 ,

This issue is likely due to how Power BI handles decimal precision in What If parameters or GENERATESERIES() when using floating point numbers. Even if you define a step like 0.01, Power BI might round or misinterpret the values due to binary floating point limitations.

Recommended Fix:

Use the CURRENCY() function to force fixed decimal precision:

Parameter = GENERATESERIES(CURRENCY(0), CURRENCY(3), CURRENCY(0.01))

This ensures that the values are treated as fixed decimal numbers, not floating point, and will resolve the rounding or mismatch issues you're seeing.

Let me know if you're using this inside a slicer or a measure — happy to help adjust it further.

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.

[jmont031]

Hi

Thanks for your message. I am afraid I am still have the problem. 0.714 is resolving to 0.719 at 3 dec. places and to 0.72 at 2 decimal places

[burakkaragoz]

That sounds like a rounding issue rather than a parameter input problem. Power BI sometimes applies automatic rounding based on the formatting of the field or visual.

Can you check the data type and format of the parameter or measure you're using? Try setting the format to show more decimal places (like 4 or 5) and see if the value is actually changing or just being rounded visually.

Also, if you're using any DAX calculations, make sure there's no implicit rounding happening in the logic.

Let me know what you're seeing in the data view vs. the visual – that might help narrow it down.

---

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
translation and formatting supported by AI

[jmont031]

Hi

I have attached more pics. I have tried as deciaml, fixed decimal etc. same result. I type 0.0714 and get 0.0719. If it was rounding why is it rounding UP from xxx4 to xxx9?. 

Thanks again

[burakkaragoz · Accepted solution]

What you're seeing is likely due to floating point precision issues. Power BI sometimes stores decimal numbers in binary format, which can cause small rounding errors – especially with values like 0.0714.

Here are a few things you can try:

1. Use ROUND([YourParameter], 4) in DAX to force the value to 4 decimal places.
2. In Power Query, apply Number.Round(YourParameter, 4) to clean it up before it hits the model.
3. Make sure the parameter is set as Decimal Number, not Fixed Decimal, and formatted to 4 decimal places.
4. As a workaround, you can also input the value as text and convert it using VALUE("0.0714").
   translation and formatting supported by AI