<?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 Re: Pivot table with custom column dimension in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Pivot-table-with-custom-column-dimension/m-p/2519738#M106321</link>
    <description>&lt;P&gt;Your approach is a nested if-loop - using pick(match()) is only a different syntax - and Qlik calculates at first all branches and picked then the first TRUE result. That is a rather unusual behaviour but it has big benefits by only a few loops with rather simple matching and the complete opposite by returning n complex calculations.&lt;/P&gt;&lt;P&gt;In other words such approach couldn't be fast. Better would be to transfer as much as possible of the calculations within the dimensionalities.&lt;/P&gt;</description>
    <pubDate>Mon, 02 Jun 2025 08:21:02 GMT</pubDate>
    <dc:creator>marcus_sommer</dc:creator>
    <dc:date>2025-06-02T08:21:02Z</dc:date>
    <item>
      <title>Pivot table with custom column dimension</title>
      <link>https://community.qlik.com/t5/App-Development/Pivot-table-with-custom-column-dimension/m-p/2517886#M105991</link>
      <description>&lt;P&gt;Hello&lt;BR /&gt;below is a screenshot of a pivot table I developed (not all of it appears in this screenshot)&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ali_hijazi_0-1747294232421.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/180502iF8232370274A7B38/image-size/medium?v=v2&amp;amp;px=400" role="button" title="ali_hijazi_0-1747294232421.png" alt="ali_hijazi_0-1747294232421.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I got on the left 20 expressions and each cell has its own number formatting, money, or percentage or integer&lt;BR /&gt;and as a column dimension I have field defined in an inline table as follows:&lt;BR /&gt;load * inline [&lt;BR /&gt;rpt_colulmn&lt;BR /&gt;1&lt;BR /&gt;2&lt;BR /&gt;3&lt;BR /&gt;4...&lt;/P&gt;&lt;P&gt;];&lt;/P&gt;&lt;P&gt;in the definition of the column dimension in the pivot table I defined the following:&lt;BR /&gt;pick(rpt_column,'Unit','Actual','Actual %', 'Budget',....)&lt;BR /&gt;&lt;BR /&gt;now in each expression I do the following&lt;BR /&gt;pick(rpt_column,&lt;/P&gt;&lt;P&gt;expression1,&lt;BR /&gt;expression2,&lt;BR /&gt;...&lt;/P&gt;&lt;P&gt;)&lt;/P&gt;&lt;P&gt;the result is correct but the table takes one minute to display result&lt;BR /&gt;is there a faster way to accomplish this?&lt;BR /&gt;kindly advise&lt;/P&gt;</description>
      <pubDate>Thu, 15 May 2025 08:03:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Pivot-table-with-custom-column-dimension/m-p/2517886#M105991</guid>
      <dc:creator>ali_hijazi</dc:creator>
      <dc:date>2025-05-15T08:03:04Z</dc:date>
    </item>
    <item>
      <title>Re: Pivot table with custom column dimension</title>
      <link>https://community.qlik.com/t5/App-Development/Pivot-table-with-custom-column-dimension/m-p/2519431#M106258</link>
      <description>&lt;P&gt;If you are using multiple match parameters in pick, it is bound to take more time to display the table,&lt;/P&gt;&lt;P&gt;one thing that you can check if you are using nested if conditions in your expression part, try to replace them with set analysis if possible.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Aditya&lt;/P&gt;</description>
      <pubDate>Thu, 29 May 2025 07:07:33 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Pivot-table-with-custom-column-dimension/m-p/2519431#M106258</guid>
      <dc:creator>Aditya_Chitale</dc:creator>
      <dc:date>2025-05-29T07:07:33Z</dc:date>
    </item>
    <item>
      <title>Re: Pivot table with custom column dimension</title>
      <link>https://community.qlik.com/t5/App-Development/Pivot-table-with-custom-column-dimension/m-p/2519671#M106308</link>
      <description>&lt;P&gt;Sometimes, the better code to implement our customizations isn't the better for the charts &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In this case, you can try to create variables for each column and line to improve speed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Bye!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 02 Jun 2025 01:51:43 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Pivot-table-with-custom-column-dimension/m-p/2519671#M106308</guid>
      <dc:creator>rafaelencinas</dc:creator>
      <dc:date>2025-06-02T01:51:43Z</dc:date>
    </item>
    <item>
      <title>Re: Pivot table with custom column dimension</title>
      <link>https://community.qlik.com/t5/App-Development/Pivot-table-with-custom-column-dimension/m-p/2519738#M106321</link>
      <description>&lt;P&gt;Your approach is a nested if-loop - using pick(match()) is only a different syntax - and Qlik calculates at first all branches and picked then the first TRUE result. That is a rather unusual behaviour but it has big benefits by only a few loops with rather simple matching and the complete opposite by returning n complex calculations.&lt;/P&gt;&lt;P&gt;In other words such approach couldn't be fast. Better would be to transfer as much as possible of the calculations within the dimensionalities.&lt;/P&gt;</description>
      <pubDate>Mon, 02 Jun 2025 08:21:02 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Pivot-table-with-custom-column-dimension/m-p/2519738#M106321</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2025-06-02T08:21:02Z</dc:date>
    </item>
  </channel>
</rss>

