Can you post the sample data to help better?
The number formatting can be controlled from Default Properties of a Measure.
Hi, this is due to workbook locale. Change to the correct locale and everything ought to work fine
Here is a small demo to understand data source locale role in interpreting your data:
I have this test here: In DK, a comma is used as thousand-separator, so we get this result
When we change locale, we get something different
Hope this helps
Appreciate the response, but I've already changed my locale to Finland but it doesn't seem to change the way Tableau interprets the data. See my other response for a sample pic of the data in question
1 of 1 people found this helpful
Is your data source a database or a flat file?
It's a database. I was given access to an anonymized database dump in the form of a .sql file (1,3 Gb) and uploaded it to localhost so I can practice with it. I therefore don't even have those options (such as text file properties) that you listed in your example above.
I should've included this information as this is relevant - if I become familiar with Tableau and start using it, it will be with databases / via sql and I assume I'll be running into issues like this in the future as well.
Changing the number format was the first thing I tried, but to no avail.
I first did that, and the result is still:
Without the number filter applied the result is just this:
So the only difference is the ,62.
This leads me back to my original question which was if I can filter the data itself somehow, because just filtering the output doesn't produce the desired results.
Is there a way for me to simply divide the result by 1000 as that would straight up produce accurate results in this particular case?
If locale won't do the work and you do not want to change schema, you can simply create a calculation field that divides everything with 1000.
You can do this in data preparation as:
or you can use reference (Which is very powerful) in your Worksheet
Reference the original to the calculated correction
After ok, then all Price will change to the reference
in the end, if you do not like having both numbers, you can hide the original
Thanks. This sorted it out. It's now producing the desired output even if the data itself still looks less than ideal. Ultimately, however, it's the output that matters and this helps me achieve a desirable output and I appreciate the answer!
Thanks for your patience and time in figuring this out.
The locale ought to have worked. Another way is to use Custom Query. Depending on your database vendo/SQL dialec, it should be possible to perform proper formatting at data preparation stage.