<?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: IF logic statement causing memory issues in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/IF-logic-statement-causing-memory-issues/m-p/428772#M159807</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Then the calculated dimension is probably just too complicated to calculate for your data set. Maybe you can change your expressions over to set analysis expressions: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sum({&amp;lt;&lt;SPAN style="color: #737373; font-family: Arial; background-color: #ffffff;"&gt;OnTrackingSheet&lt;/SPAN&gt;={'Yes'},&lt;SPAN style="color: #737373; font-family: Arial; background-color: #ffffff;"&gt;Over500k&lt;/SPAN&gt;={'Yes'},Progress-={'Closed'},RAG={'Red'},Active={'Active'}&amp;gt;} MyValue)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The expression editor will flag -= as wrong syntax, but that's a bug in the expression editor. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, I'd replace 'Yes' and 'No' values in the script with dual values so they have a numeric value as well. Calculations on numeric values are faster than string comparisons. See &lt;A href="http://qlikviewnotes.blogspot.nl/2013/05/assigning-dual-values-with-dummy-load.html"&gt;this blog post&lt;/A&gt; for a quick fix.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 31 May 2013 11:49:17 GMT</pubDate>
    <dc:creator>Gysbert_Wassenaar</dc:creator>
    <dc:date>2013-05-31T11:49:17Z</dc:date>
    <item>
      <title>IF logic statement causing memory issues</title>
      <link>https://community.qlik.com/t5/QlikView/IF-logic-statement-causing-memory-issues/m-p/428769#M159804</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a Straight Table and I want to restrict the data displayed based on the following logic within a Calculated Dimension (so that I can suppress when value is null):&lt;/P&gt;&lt;P&gt;=IF(OnTrackingSheet='Yes' OR Over500k?='Yes', ID, &lt;/P&gt;&lt;P&gt;IF(Progress&amp;lt;&amp;gt;'Closed' AND RAG='Red' AND Active='Active', ID, &lt;/P&gt;&lt;P&gt;NULL()))&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This causes the error message box:&lt;/P&gt;&lt;P&gt;"Out of virtual and / or logical memory allocating 2MB"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Straight Table then breaks displaying error:&lt;/P&gt;&lt;P&gt;"Allocated memory exceeded"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is how do I retain this logic in a more efficient manner that doesn't kill the object?&lt;/P&gt;&lt;P&gt;The data required for the above IF statement is spread across four tables. Based on a process of elimination the &lt;STRONG&gt;Over500k?='Yes'&lt;/STRONG&gt; com&lt;A&gt;&lt;/A&gt;ponent seems to be the trouble-maker. Once &lt;STRONG&gt;Over500k?='Yes'&lt;/STRONG&gt; is removed everything works ok. This, needless to say, is not acceptable from a user perspective.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As they are OR statements I cannot use selection triggers.&lt;/P&gt;&lt;P&gt;I am open to creating this logic in the script at load time however I have never linked up multiple tables like this before....is this even feasible?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help greatly appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 May 2013 11:14:16 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/IF-logic-statement-causing-memory-issues/m-p/428769#M159804</guid>
      <dc:creator />
      <dc:date>2013-05-31T11:14:16Z</dc:date>
    </item>
    <item>
      <title>Re: IF logic statement causing memory issues</title>
      <link>https://community.qlik.com/t5/QlikView/IF-logic-statement-causing-memory-issues/m-p/428770#M159805</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try [&lt;STRONG style="background-color: #ffffff; color: #737373; font-family: Arial;"&gt;Over500k?&lt;/STRONG&gt;] instead of &lt;STRONG style="background-color: #ffffff; color: #737373; font-family: Arial;"&gt;Over500k?&lt;/STRONG&gt;. If that doesn't work try renaming the field in the script to for example IsOver500k. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 May 2013 11:19:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/IF-logic-statement-causing-memory-issues/m-p/428770#M159805</guid>
      <dc:creator>Gysbert_Wassenaar</dc:creator>
      <dc:date>2013-05-31T11:19:28Z</dc:date>
    </item>
    <item>
      <title>Re: IF logic statement causing memory issues</title>
      <link>https://community.qlik.com/t5/QlikView/IF-logic-statement-causing-memory-issues/m-p/428771#M159806</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the suggestion Gysbert.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have renamed to Over500k and [Over500k] however the issue remains.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 May 2013 11:32:07 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/IF-logic-statement-causing-memory-issues/m-p/428771#M159806</guid>
      <dc:creator />
      <dc:date>2013-05-31T11:32:07Z</dc:date>
    </item>
    <item>
      <title>Re: IF logic statement causing memory issues</title>
      <link>https://community.qlik.com/t5/QlikView/IF-logic-statement-causing-memory-issues/m-p/428772#M159807</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Then the calculated dimension is probably just too complicated to calculate for your data set. Maybe you can change your expressions over to set analysis expressions: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sum({&amp;lt;&lt;SPAN style="color: #737373; font-family: Arial; background-color: #ffffff;"&gt;OnTrackingSheet&lt;/SPAN&gt;={'Yes'},&lt;SPAN style="color: #737373; font-family: Arial; background-color: #ffffff;"&gt;Over500k&lt;/SPAN&gt;={'Yes'},Progress-={'Closed'},RAG={'Red'},Active={'Active'}&amp;gt;} MyValue)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The expression editor will flag -= as wrong syntax, but that's a bug in the expression editor. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, I'd replace 'Yes' and 'No' values in the script with dual values so they have a numeric value as well. Calculations on numeric values are faster than string comparisons. See &lt;A href="http://qlikviewnotes.blogspot.nl/2013/05/assigning-dual-values-with-dummy-load.html"&gt;this blog post&lt;/A&gt; for a quick fix.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 May 2013 11:49:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/IF-logic-statement-causing-memory-issues/m-p/428772#M159807</guid>
      <dc:creator>Gysbert_Wassenaar</dc:creator>
      <dc:date>2013-05-31T11:49:17Z</dc:date>
    </item>
    <item>
      <title>Re: IF logic statement causing memory issues</title>
      <link>https://community.qlik.com/t5/QlikView/IF-logic-statement-causing-memory-issues/m-p/428773#M159808</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try this&lt;/P&gt;&lt;P&gt;Aggr(Only({$&amp;lt;&lt;SPAN style="color: #737373; font-family: Arial; background-color: #ffffff;"&gt;OnTrackingSheet&lt;/SPAN&gt;={'Yes'}+&lt;SPAN style="color: #737373; font-family: Arial; background-color: #ffffff;"&gt;Over500k?&lt;/SPAN&gt;={'Yes'},&lt;SPAN style="color: #737373; font-family: Arial; background-color: #ffffff;"&gt;Progress&lt;/SPAN&gt;-={'Closed'}&amp;gt;}*RAG={'Red'}*Active={'Active'} ID), ID)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 May 2013 12:00:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/IF-logic-statement-causing-memory-issues/m-p/428773#M159808</guid>
      <dc:creator>er_mohit</dc:creator>
      <dc:date>2013-05-31T12:00:08Z</dc:date>
    </item>
  </channel>
</rss>

