Locale influences CSV upload to datatype?
We have to upload a CSV-file to fill our datatype on the acceptance environment.
As developers, we only have access to dev and test, which means someone else has to fill the acceptance environment.
On the acceptance environment the file I extracted from Dev, Pega was unable to parse.
Turns out that the user on Acceptance was on a different locale (nl_NL) compared to me (en_EN).
So it seems that on the Dutch locale, Pega requires a semicolon as a separating symbol, on the English local it requires a comma.
After the user switched to the en_EN locale, the upload completed without issues.
Has anyone else encountered this problem or other unexpected behaviour related to Locale settings?
Also, what is the cause of this different behaviour?
Accepted Solution
Pegasystems Inc.
IN
check the decision table pzGetLocaleListSeperator to get correct separator which will be allowed for each locale.
Few locale's have comma ',' as decimal separator for double values that's why for those locales mapped semicolon ';' as a csv separator.