DialGauge Problems

[Anonymous]

Hey there,

i have reviewd the behaviour of my DialGauge (newest version with Desktop BI current version) 

- I added a simple table on my SQL Server with directquery.

- All fields are formatted with fielddatatype = Money

- I´m running Desktop BI, SQL-Server and local OS in German

I can´t understand why a certain behaviour changes from one day to the other. It seems that some background stuff changed around Jan. 8th 2019.   I guess that the change is due to the German (or maybe European) dataformat. 

As you can see on my example ',' and '." are different. If you set Toggle  to ON, you see that the values get completely wrong.

 

I wonder why nobody else is getting similar problems as I report here. Unfortunately, the responsible Author is not replying to my request.

Can someone please try to reproduce this on the US site maybe 😊

Claus

[v-lili6-msft]

hi, @Anonymous

After my research, the decimal point and the thousand semicolon of most visuals are based on local region setting of computer.

For example:

In my computer, my region is US. It works well like others.

But when I change the region is German, other visuals have changed with the computer, only DialGauge keep the same format.

http://schoennie.blogspot.com/2018/11/thousand-separator-and-decimal.html

So If you run it with US region, it will work as others, and it seems that it doesn't change with local region of computer.

Since this visualization is published by CloudFronts Technologies, please contact them for support.

Please understand that this link is provided “AS IS” with no warranties or guarantees of content changes, and confers no rights.

Best Regards,
Lin

[Anonymous]

Hi Lin, thx for your effort. I will get in touch with the Developer.