<?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: Performance Issue with AdHoc Pivot Table using Conditionals in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Performance-Issue-with-AdHoc-Pivot-Table-using-Conditionals/m-p/460809#M1272335</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No thoughts at all on this?&amp;nbsp; I was hoping for something.&amp;nbsp; Does anyone use the conditionals like this on pivot tables and if so how many fields approximately?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 25 Mar 2013 10:32:35 GMT</pubDate>
    <dc:creator />
    <dc:date>2013-03-25T10:32:35Z</dc:date>
    <item>
      <title>Performance Issue with AdHoc Pivot Table using Conditionals</title>
      <link>https://community.qlik.com/t5/QlikView/Performance-Issue-with-AdHoc-Pivot-Table-using-Conditionals/m-p/460808#M1272332</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have a report that is more of a AdHoc for our users.&amp;nbsp; The report currently has 54 Dimensions with a Enable Conditional and 9 Expressions using Conditional to create this report.&amp;nbsp; The user has a picklist to choose the fields they want to display for the report.&amp;nbsp; The user reduced data down to 4 months worth of Labor data which is about 150,000 rows of data.&amp;nbsp; When the user picks no more than 3-4 fields the report just slows down considerably.&amp;nbsp; Has anyone else tried to use the conditional feature in this way and seen these type of performance issues?&amp;nbsp; I can create a pivot table with those selections specifically and the report flies of course.&amp;nbsp; All this is done in Ajax btw but even in my client I notice performance is horrible.&amp;nbsp; Just showing the user and their total hours which is about 4000 rows of data is horrible in this report.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Performance-Issue-with-AdHoc-Pivot-Table-using-Conditionals/m-p/460808#M1272332</guid>
      <dc:creator />
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: Performance Issue with AdHoc Pivot Table using Conditionals</title>
      <link>https://community.qlik.com/t5/QlikView/Performance-Issue-with-AdHoc-Pivot-Table-using-Conditionals/m-p/460809#M1272335</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No thoughts at all on this?&amp;nbsp; I was hoping for something.&amp;nbsp; Does anyone use the conditionals like this on pivot tables and if so how many fields approximately?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Mar 2013 10:32:35 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Performance-Issue-with-AdHoc-Pivot-Table-using-Conditionals/m-p/460809#M1272335</guid>
      <dc:creator />
      <dc:date>2013-03-25T10:32:35Z</dc:date>
    </item>
  </channel>
</rss>

