topic Why is Qlik Sense setting default formats? in App Development

Why is Qlik Sense setting default formats?

chrislemm — Fri, 02 Nov 2018 13:34:29 GMT

Dear Qlik Community,

today I received a question from one of our qlik sense customers I can't answer. Our customer has got an oracle view where some numeric values are converted to the german standard format (for example from 1,000.49 to 1.000,49). The oracle server shows the correctly formatted values inside the view fields:

Our customer uses Qlik Sense to load these data and write it back to a .csv-file. When building the script we can't load the fieldnames by name directly, because the view is constantly changing, so we load the script using *.

Example:

Table:

select

FROM "View";

Store Tableinto [lib://Folder/file.csv](txt, delimiter is ';');

This works fine. Qlik Sense exports the csv including the requested data. But when viewing the data inside the csv-file, we see:

Why is Qlik Sense reformatting the values? Is there anything we can setup to load the data in exact the same way as they are displayed in oracle? Without using the num(field) function or any function that required a field-relation?

Greetings

Re: Why is Qlik Sense setting default formats?

vunguyenq89 — Fri, 02 Nov 2018 13:55:06 GMT

It is affected by the default thousand separator and decimal separator in your locale settings. To have your desired format, try setting the initiation variables at the beginning of your reload script:

SET ThousandSep='.';

SET DecimalSep=',';

Re: Why is Qlik Sense setting default formats?

chrislemm — Mon, 05 Nov 2018 07:15:46 GMT

Hey Vu,

thank your for your reply. The Thousand and Decimalseperator are set to the german standard by default:

SET ThousandSep='.';

SET DecimalSep=',';

So apparently these are not effecting the format.

Best regards