Gauge visual shows different number of decimals in dashboard than in Desktop

[helenah]

I have used the Gauge visual in showing some results in Power BI. Up until recently, it has worked well. One ogf the report users just notified that the Gauge shows currently two decimals for all values although in Desktop there are no decimals and I have also made sure that the Format is set to 0 decimals and even the format is "Whole number".

Has anyone else noticed the same and is this a bug, or something I can do to fix it? The report now looks very stupid.

[v-caliao-msft]

Hi@helenah,

Which data type are you using? Could you please provide us a screenshoot of you source table? I have tested it on my local environment, we cannot reproduce this issue.

Regards,

Charlie Liao

[helenah]

Hi @v-caliao-msft,

Data type is whole number. I forgot to mention, that I have the average of that field in the gauge. I made a simple example power bi file which I could share with you by email.

Meanwhile, snapshots of my data and report below.

This is the data tableThis is how the gauge is definedThis is again the data type of the same field in the report view

[helenah]

Hi,

This is a link to an example Power BI file I created to show this problem:

https://drive.google.com/open?id=0B47qZ88gRy8EcjIwZl9GTkN1YkE

@v-caliao-msft

Are you able to reproduce this issue? Is it a bug or can I fix ift somehow?

[v-caliao-msft · Accepted solution]

Hi @helenah,

He issue is caused by average function. Based on my tested, the Average function in Value will keep two decimals in Power BI services. In order to avoid this issue, you can create measure like
AverageScore = AVERAGE(Table1[Score])
AverageMin = AVERAGE(Table1[Min])
Averagemax = AVERAGE(Table1[Max])

Besides, I will report this issue and hope this will be resolved in next release.

Regards,

Charlie Liao

[helenah]

Thank you @v-caliao-msft for replying. The average used to work OK in the previous PowerBI Desktop version, it is only the recent one that shows the decimals with averages in Gauge. I have had the same report running for months and only now it does not work as expected. Really hoping it will be fixed soonest. Your solution is an OK workaround, but with the number of Gauges I have on my report, it is just too much work.

br,

Helena