Forum Discussion
Auto display units not working when no decimals
Hi Anonymous,
Based on my test, in a KPI visual, the currency field contains decimal will display in corresponding units automatically. While the currency field without decimal will display as a whole value without any unit. But as there is a OOTB feature called Display Units in KPI visuals, we can always display values in prefer units by setting this property. I don't think it's a matter to set this property as a prefer value.
In addition, in a table or matrix visual, there is no buit-in property which is the same as the "Display Units" in KPI visuals. For this issue, you can post a idea in Power Ideas forum.
If you have any question, please feel free to ask.
Best Regards,
Qiuyun Yu
I think I'll open a bug then. It doesn't make sense that the visual is showing a whole number when there's no decimals. I can't either choose manually the display unit since I have a report that can show sales of the total organization (in billions) as well as sales of a single site (in thousands).
As for the table visual, it was only an example. I don't want decimals anywhere (other visuals, tooltips, etc.). While it would be great to have a "number of decimals shown" property in the table and matrix visual, it would not fix my problem.
Currently, I'm creating my measures twice. One with decimals for the KPI and other similar visuals and one without decimals for the others. Kind of stupid if you ask me.
- v-qiuyu-msft10 years ago
Community Support
Hi Anonymous,
You can send a feedback by clicking "Send a frown" like below:
Best Regards,
Qiuyun Yu- Anonymous10 years agoNot applicable
Yeah I know. Just wished that somebody had an answer rather than waiting for Microsoft support...
- cmn10 years ago
Kudo Collector
Hi Anonymous. Did you end up with a resolution for this? I am having the same problem - SSAS tabular on premise connection with measures that are formatted to have no decimals. In this scenario, the Auto formatting option on the KPI is not working. This is obviously a bug. Did you end up raising a ticket for this?