I’ve got a big issue. Unfortunately, this customer has used almost no ETL, which is why I’m looking for a better solution than using a replace everywhere. The situation is as follows:
On-prem, the customer has a Progress OpenEdge 32-bit ODBC connection. For a large number of fields, the data type is numeric. On-prem, Qlik automatically converts the numeric values to a comma according to my settings.
SET ThousandSep='.';
SET DecimalSep=',';
SET MoneyThousandSep='.';
SET MoneyDecimalSep=',';
SET MoneyFormat='€ #.##0,00;€ #.##0,00-';
Unfortunately, when I use a gateway, I don’t get a data type back and Qlik shows the value with a . instead of a , . For the gateway, I’m using a newer driver and 64-bit instead of 32-bit. The SQL syntax is set to SAP HANA SQL syntax, because that's the only one that works.
A data gateway is an intermediary between the source and the target - and it could have it's own region-settings and char-sets respectively a limited set of supported ones - and it may touch the data directly (with potentially changes) or not.
There are a lot of issues possible which may hard to detect and maybe more difficult to bypass or to solve them. Helpful could be to avoid all formatting and using only pure integer/long numbers and/or to define all region/interpretation-settings explicitly.
