When I import my CSV in which a column with numbers (xxxx,yy) it is not recognised as numberfields. I tried to change the data type in Excel (number, currency,) but it doesn’t work. I also tried to make an import with numbers without ‘something behind the comma’. But alas.
I want to do summation etc with these numbers. I really don’t know how to make this work.
Does anyone have a suggestion how to fix this.
I’m new in working with Metabase, so hopefully it is an easy solution.
Double-check that the column types are set correctly in table metadata for the model created for the CSV. You can access this by clicking on the model, clicking the 3 dots menu in the upper right, and selecting ‘Edit metadata.’
Are you in a locale that uses comma as a decimal separator?
If so, what language is Metabase running as? This can be found in Admin → Tools→Diagnostic Info, under the system-info heading, called user.language.
If these are different then you’ll need to output the numbers in the format expected for the locale Metabase is running in. If it’s running in en for instance, set your cell formats to use period as a decimal separator. (I’m not in a position to test this.)
Thanks, it seems that there was a problem somewhere in the column. They are calculated numbers, and there where a couple of ‘N/A’ in them. After I removed them, it worked.
With CSV import, before you use the real csv file, create a sample that has perfect data in it. Numerics rather than integers if you don’t want an integer column, strings that are long enough for the largest you’ll ever expect etc. Than do the import.
For dates, I’ve given up. I just import as varchar and cast later. Sometimes, life is too short, especially when users muddle up date/time formats themselves.