Forum Discussion
what if parameter
Hi hidenseek9，
By confirmed by PG, the cause of this issue is that your parameter range is too big. We have a fix that will allow up to 3500 (or maybe even 5000 if perf looks good). Should land in a couple of months.
Best Regards,
Cherry
Hi hidenseek9,
Does this issue exist all the pbix file or the single one?
From my tests with two Power BI Versions, the what If parameter works well. Here are the pictures of the test result:
Picture1 is tested on the version February 2018
Picture2 is tested on the version January 2018
If your scenario is clicking the number 1, it will appear like this:
For the workaround, you may try to use the Fixed Decimal number, it will return the number you type in.
You could also refer to my test pbix file on OneDrive: https://1drv.ms/u/s!AhDc2ZBZkwhXgQDbIr2uqKlq1kqC
Since I cannot reproduce the same issue on my environment.
If you still cannot fix the issue, could you share a dummy pbix file which can reproduce the issue, so that we can help further investigate on it? You can upload it to OneDrive or Dropbox and post the link here. Do mask sensitive data before uploading.)
Best Regards,
Cherry
Thank you for your response.
Yes it happens with all pbix files unfortunately.
It also happens with your test pbix file as well.
When I select 1.5, it returns 1.4 and when I select 120.8, it returns 120.7.
This means it may not be the problem with just my pbix file,
but a bug at Power BI level??
Many thanks,
H
Hi hidenseek9，
By confirmed by PG, the cause of this issue is that your parameter range is too big. We have a fix that will allow up to 3500 (or maybe even 5000 if perf looks good). Should land in a couple of months.
Best Regards,
Cherry
