<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic PixelPerfect report ignores Qlik script DecimalSep and forces comma instead of period in XRLabel FormatString in Reporting Service &amp; Alerting</title>
    <link>https://community.qlik.com/t5/Reporting-Service-Alerting/PixelPerfect-report-ignores-Qlik-script-DecimalSep-and-forces/m-p/2553151#M2816</link>
    <description>&lt;P data-path-to-node="3"&gt;Hi everyone,&lt;/P&gt;
&lt;P data-path-to-node="4"&gt;I am experiencing an issue with decimal formatting in a &lt;STRONG data-index-in-node="56" data-path-to-node="4"&gt;PixelPerfect&lt;/STRONG&gt; template in Qlik Cloud.&lt;/P&gt;
&lt;P data-path-to-node="5"&gt;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:&lt;/P&gt;
&lt;DIV class="code-block ng-tns-c3982514797-118 ng-animate-disabled ng-trigger ng-trigger-codeBlockRevealAnimation" data-ved="0CAAQhtANahgKEwjFra_ShtCVAxUAAAAAHQAAAAAQ7QU" data-hveid="0"&gt;
&lt;DIV class="formatted-code-block-internal-container ng-tns-c3982514797-118"&gt;
&lt;DIV class="animated-opacity ng-tns-c3982514797-118"&gt;
&lt;DIV class="code-block-decoration header-formatted gds-emphasized-body-m ng-tns-c3982514797-118 ng-star-inserted"&gt;SET ThousandSep=',';&lt;BR /&gt;SET DecimalSep='.';&lt;/DIV&gt;
&lt;DIV class="code-block-decoration header-formatted gds-emphasized-body-m ng-tns-c3982514797-118 ng-star-inserted"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="code-block-decoration header-formatted gds-emphasized-body-m ng-tns-c3982514797-118 ng-star-inserted"&gt;
&lt;P data-path-to-node="7"&gt;However, when designing my PixelPerfect report, any &lt;CODE data-index-in-node="52" data-path-to-node="7"&gt;XRLabel&lt;/CODE&gt; component using custom formatting displays a comma instead of a period. For example, using a Text Format String like &lt;CODE data-index-in-node="177" data-path-to-node="7"&gt;{0:.00}&lt;/CODE&gt; or &lt;CODE data-index-in-node="188" data-path-to-node="7"&gt;{0:.##}&lt;/CODE&gt; outputs &lt;CODE data-index-in-node="204" data-path-to-node="7"&gt;,21&lt;/CODE&gt; instead of &lt;CODE data-index-in-node="219" data-path-to-node="7"&gt;.21&lt;/CODE&gt;.&lt;/P&gt;
&lt;P data-path-to-node="8"&gt;It seems the reporting engine is overriding the Qlik application's &lt;CODE data-index-in-node="67" data-path-to-node="8"&gt;DecimalSep&lt;/CODE&gt; variable and using a culture-dependent layout based on the cloud tenant region or server locale.&lt;/P&gt;
&lt;P data-path-to-node="10"&gt;Is there a definitive way to force a literal period (&lt;CODE data-index-in-node="53" data-path-to-node="10"&gt;.&lt;/CODE&gt;) as the decimal separator directly within the PixelPerfect designer properties, or is this a known limitation of the cloud reporting service locale settings?&lt;/P&gt;
&lt;P data-path-to-node="11"&gt;Any help or workarounds to solve this without modifying the format in every single Qlik expression beforehand would be highly appreciated.&lt;/P&gt;
&lt;P data-path-to-node="12"&gt;Thanks in advance!&lt;/P&gt;
&lt;H3 data-path-to-node="14"&gt;&amp;nbsp;&lt;/H3&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
    <pubDate>Mon, 13 Jul 2026 22:31:40 GMT</pubDate>
    <dc:creator>07734</dc:creator>
    <dc:date>2026-07-13T22:31:40Z</dc:date>
    <item>
      <title>PixelPerfect report ignores Qlik script DecimalSep and forces comma instead of period in XRLabel FormatString</title>
      <link>https://community.qlik.com/t5/Reporting-Service-Alerting/PixelPerfect-report-ignores-Qlik-script-DecimalSep-and-forces/m-p/2553151#M2816</link>
      <description>&lt;P data-path-to-node="3"&gt;Hi everyone,&lt;/P&gt;
&lt;P data-path-to-node="4"&gt;I am experiencing an issue with decimal formatting in a &lt;STRONG data-index-in-node="56" data-path-to-node="4"&gt;PixelPerfect&lt;/STRONG&gt; template in Qlik Cloud.&lt;/P&gt;
&lt;P data-path-to-node="5"&gt;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:&lt;/P&gt;
&lt;DIV class="code-block ng-tns-c3982514797-118 ng-animate-disabled ng-trigger ng-trigger-codeBlockRevealAnimation" data-ved="0CAAQhtANahgKEwjFra_ShtCVAxUAAAAAHQAAAAAQ7QU" data-hveid="0"&gt;
&lt;DIV class="formatted-code-block-internal-container ng-tns-c3982514797-118"&gt;
&lt;DIV class="animated-opacity ng-tns-c3982514797-118"&gt;
&lt;DIV class="code-block-decoration header-formatted gds-emphasized-body-m ng-tns-c3982514797-118 ng-star-inserted"&gt;SET ThousandSep=',';&lt;BR /&gt;SET DecimalSep='.';&lt;/DIV&gt;
&lt;DIV class="code-block-decoration header-formatted gds-emphasized-body-m ng-tns-c3982514797-118 ng-star-inserted"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="code-block-decoration header-formatted gds-emphasized-body-m ng-tns-c3982514797-118 ng-star-inserted"&gt;
&lt;P data-path-to-node="7"&gt;However, when designing my PixelPerfect report, any &lt;CODE data-index-in-node="52" data-path-to-node="7"&gt;XRLabel&lt;/CODE&gt; component using custom formatting displays a comma instead of a period. For example, using a Text Format String like &lt;CODE data-index-in-node="177" data-path-to-node="7"&gt;{0:.00}&lt;/CODE&gt; or &lt;CODE data-index-in-node="188" data-path-to-node="7"&gt;{0:.##}&lt;/CODE&gt; outputs &lt;CODE data-index-in-node="204" data-path-to-node="7"&gt;,21&lt;/CODE&gt; instead of &lt;CODE data-index-in-node="219" data-path-to-node="7"&gt;.21&lt;/CODE&gt;.&lt;/P&gt;
&lt;P data-path-to-node="8"&gt;It seems the reporting engine is overriding the Qlik application's &lt;CODE data-index-in-node="67" data-path-to-node="8"&gt;DecimalSep&lt;/CODE&gt; variable and using a culture-dependent layout based on the cloud tenant region or server locale.&lt;/P&gt;
&lt;P data-path-to-node="10"&gt;Is there a definitive way to force a literal period (&lt;CODE data-index-in-node="53" data-path-to-node="10"&gt;.&lt;/CODE&gt;) as the decimal separator directly within the PixelPerfect designer properties, or is this a known limitation of the cloud reporting service locale settings?&lt;/P&gt;
&lt;P data-path-to-node="11"&gt;Any help or workarounds to solve this without modifying the format in every single Qlik expression beforehand would be highly appreciated.&lt;/P&gt;
&lt;P data-path-to-node="12"&gt;Thanks in advance!&lt;/P&gt;
&lt;H3 data-path-to-node="14"&gt;&amp;nbsp;&lt;/H3&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Mon, 13 Jul 2026 22:31:40 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Reporting-Service-Alerting/PixelPerfect-report-ignores-Qlik-script-DecimalSep-and-forces/m-p/2553151#M2816</guid>
      <dc:creator>07734</dc:creator>
      <dc:date>2026-07-13T22:31:40Z</dc:date>
    </item>
    <item>
      <title>Re: PixelPerfect report ignores Qlik script DecimalSep and forces comma instead of period in XRLabel FormatString</title>
      <link>https://community.qlik.com/t5/Reporting-Service-Alerting/PixelPerfect-report-ignores-Qlik-script-DecimalSep-and-forces/m-p/2553452#M2823</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;Unfortunately, there is no designer property that forces a literal decimal separator independently of the report culture.&lt;/P&gt;&lt;P&gt;Possible workarounds&lt;/P&gt;&lt;P&gt;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).&lt;/P&gt;&lt;P&gt;1.Convert the value to text if a fixed display format is required.&lt;/P&gt;&lt;P&gt;2.⁠Review the tenant/report locale settings to see if they match the desired regional format.&lt;/P&gt;&lt;P&gt;If none of these options are suitable,&lt;/P&gt;&lt;P&gt;3⁠open a Qlik Support case to determine whether this is a product limitation or a defect in the current Qlik Cloud Reporting release.&lt;/P&gt;</description>
      <pubDate>Sun, 19 Jul 2026 16:59:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Reporting-Service-Alerting/PixelPerfect-report-ignores-Qlik-script-DecimalSep-and-forces/m-p/2553452#M2823</guid>
      <dc:creator>Chanty4u</dc:creator>
      <dc:date>2026-07-19T16:59:22Z</dc:date>
    </item>
  </channel>
</rss>

