Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi everyone,
I am experiencing an issue with decimal formatting in a PixelPerfect template in Qlik Cloud.
In my Qlik Sense application script, my regional variables are correctly set to use a period as the decimal separator and a comma for thousands:
However, when designing my PixelPerfect report, any XRLabel component using custom formatting displays a comma instead of a period. For example, using a Text Format String like {0:.00} or {0:.##} outputs ,21 instead of .21.
It seems the reporting engine is overriding the Qlik application's DecimalSep variable and using a culture-dependent layout based on the cloud tenant region or server locale.
Is there a definitive way to force a literal period (.) as the decimal separator directly within the PixelPerfect designer properties, or is this a known limitation of the cloud reporting service locale settings?
Any help or workarounds to solve this without modifying the format in every single Qlik expression beforehand would be highly appreciated.
Thanks in advance!
Hi
Unfortunately, there is no designer property that forces a literal decimal separator independently of the report culture.
Possible workarounds
Format the value in the Qlik load script or chart expression before passing it to the report (for example, using Num() with the required format).
1.Convert the value to text if a fixed display format is required.
2.Review the tenant/report locale settings to see if they match the desired regional format.
If none of these options are suitable,
3open a Qlik Support case to determine whether this is a product limitation or a defect in the current Qlik Cloud Reporting release.
Hi
Unfortunately, there is no designer property that forces a literal decimal separator independently of the report culture.
Possible workarounds
Format the value in the Qlik load script or chart expression before passing it to the report (for example, using Num() with the required format).
1.Convert the value to text if a fixed display format is required.
2.Review the tenant/report locale settings to see if they match the desired regional format.
If none of these options are suitable,
3open a Qlik Support case to determine whether this is a product limitation or a defect in the current Qlik Cloud Reporting release.