<?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: protect out off memory in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/protect-out-off-memory/m-p/1764432#M591217</link>
    <description>&lt;P&gt;Maybe optimizing the UI and the datamodel may help - things like avoiding if-loops, aggr-constructs, interrecord-functions and ensuring that all relevant fields come from a single table ...&lt;/P&gt;&lt;P&gt;If this is really not an option you may add a calculation-condition on your objects, something like:&lt;/P&gt;&lt;P&gt;count(distinct dim1&amp;amp;dim2&amp;amp;dim3)&amp;lt;10000&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;</description>
    <pubDate>Wed, 25 Nov 2020 15:20:06 GMT</pubDate>
    <dc:creator>marcus_sommer</dc:creator>
    <dc:date>2020-11-25T15:20:06Z</dc:date>
    <item>
      <title>protect out off memory</title>
      <link>https://community.qlik.com/t5/QlikView/protect-out-off-memory/m-p/1764411#M591216</link>
      <description>&lt;P&gt;tabel&amp;nbsp; loaded at start is large(qvd type)&amp;nbsp; , normaly user&amp;nbsp; need to show only a part of data, like&amp;nbsp; 1 year, however it happens he clicks on button clear all choices he could make,&amp;nbsp; then qlik starts reading , dislaying all years, and will hang in memort error&lt;/P&gt;&lt;P&gt;not responding anymore&lt;/P&gt;&lt;P&gt;how sowe way to make sure when he clears all&amp;nbsp; somehow keep at minumum 1 year or other item filled with a fixed value like this year only&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 17:46:38 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/protect-out-off-memory/m-p/1764411#M591216</guid>
      <dc:creator>JACKNIEKERK</dc:creator>
      <dc:date>2024-11-16T17:46:38Z</dc:date>
    </item>
    <item>
      <title>Re: protect out off memory</title>
      <link>https://community.qlik.com/t5/QlikView/protect-out-off-memory/m-p/1764432#M591217</link>
      <description>&lt;P&gt;Maybe optimizing the UI and the datamodel may help - things like avoiding if-loops, aggr-constructs, interrecord-functions and ensuring that all relevant fields come from a single table ...&lt;/P&gt;&lt;P&gt;If this is really not an option you may add a calculation-condition on your objects, something like:&lt;/P&gt;&lt;P&gt;count(distinct dim1&amp;amp;dim2&amp;amp;dim3)&amp;lt;10000&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;</description>
      <pubDate>Wed, 25 Nov 2020 15:20:06 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/protect-out-off-memory/m-p/1764432#M591217</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2020-11-25T15:20:06Z</dc:date>
    </item>
    <item>
      <title>Re: protect out off memory</title>
      <link>https://community.qlik.com/t5/QlikView/protect-out-off-memory/m-p/1764954#M591218</link>
      <description>&lt;P&gt;indeed we should optimize&lt;/P&gt;</description>
      <pubDate>Fri, 27 Nov 2020 13:55:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/protect-out-off-memory/m-p/1764954#M591218</guid>
      <dc:creator>JACKNIEKERK</dc:creator>
      <dc:date>2020-11-27T13:55:49Z</dc:date>
    </item>
  </channel>
</rss>

