what- If parameter User Input rounds off incorrectly

deevs afaik it is a known issue and there is a bug reported on issue forum, do put your comments on the issue so that it can be solved. I don't have the link to the post of the issue but you can find it on issue forum here.

Hello deevs  as you can see, you may have the same problem and include or relate to the power bi forum according to the following links:

https://community.powerbi.com/t5/Issues/bug-What-If-with-decimal-numbers/idc-p/1173208#M58316
https://community.powerbi.com/t5/Desktop/bug-What-If-with-decimal-numbers/m-p/1158010#M524368

after that I contacted the power bi support and I was answered:

_Hi Afonso,

Thank you for your time in teams meeting.

We apologize for the inconvenience caused.

Summary of the call.

Issue: What if parameter with decimal numbers not working as expected.

1.After getting this case, we analyzed from my end.

2.Raised a high severity ticket to the Product team.

3.They confirmed that,

a. The problem comes from the number of values the visual is retrieving.

b. So if there is more than 1002 different values, some may not be taken.

c. Anything with more than 1002 values will show the rounding problem.

d. This visual does not have a hi-density mode that would take more samples.e. It’s an idea to submit to the Ideas web site.

The Product team will take the priority of the deployment based on the votes polled for the idea. The idea which polled more votes they will take as priority.

Our Product team pushes improvements and features on weekly basis. These improvements are planned well in advance. But there are some of the improvements which will have lot of dependencies due to which it takes long time and sometimes it becomes extremely hard for us to define an ETA even though we have a road map of improving the feature. We hope you understand the complexity here. Our focus is always on improving customer experience and giving what customer is looking for sooner or later._

basically when you have more than 1002 values ​​the visual cannot behave in the correct format, causing the bug.

unfortunately, we need a correction as soon as possible, since many companies here in Brazil use this functionality frequently, but until today microsoft has not performed the correction.

Hi deevs ,

I found that you have an workaround on this problem from another post. Could you share us a pibx template?

Best Regards,

Icey

If you've reached this thread searching for help,

Power BI now offers a workaround: Fixed decimal numbers.

Victory!

This forces the decimal number to remain in the correct form throughout GENERATESERIES()- by using the CURRENCY() function on each value:

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