Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
I have discovered a bug with the What If parameter.
Link: https://docs.microsoft.com/en-us/power-bi/desktop-what-if
Use Case: Calculating how much cost is tied to computer memory. We want to understand how increases or decreases of memory cost affect our bottom line. This will eventually expand to software, storage, and other costs.
Data: We generate a list of servers with the amount of memory installed. We list the computer name, the amount of memory (GB), and we know the cost per GB (current default is $6.24 USD).
What If Measures / Series: We format the series using 'Fixed Decimal Point' or 'Decimal', and format the measure using 'Decimal' (which is automatically generated, and we cannot change it).
Observations: In this use case, using either Fixed Decimal or regular Decimal, we've observed that what we type into the field is not what happens in the measure. If the new measure value is above 6.24; it appears to incrementally increase at 0.05, rather than give us the actual result. Therefore, the resulting visualization is incorrect. When the new value is entered, it behaves as if it is a float, rather than a decimal or fixed decimal. Even with a shortened range (0.00 to 15.00, incrementing by 0.01), we still encounter problems.
Based on my test, I cannot reproduce the same issue. You may try to update the version of desktop. It’s better to share your data sample file. You can upload it to OneDrive or Dropbox and post the link here.
Regards,
Cherie
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
107 | |
98 | |
78 | |
66 | |
53 |
User | Count |
---|---|
144 | |
104 | |
100 | |
86 | |
64 |