<?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: how to use App Metadata Analyzer to identify what causes AAALR log entry in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/how-to-use-App-Metadata-Analyzer-to-identify-what-causes-AAALR/m-p/2493053#M102282</link>
    <description>&lt;P&gt;There are a couple of discussions in this topic already in the community pages, but none who can explicitly explain the AAALR. It might be as an earlier community member &lt;A href="https://community.qlik.com/t5/QlikView-App-Dev/SE-LOG-when-AAALR-6-186927-is-greater-than-1-000000-we-suggest/m-p/934774/highlight/true#M322828" target="_self"&gt;suggests&lt;/A&gt;, sharing the details around AAALR would also reveal core secrets about Qliks engine.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But as far as I understand it can be related to GUI calculations and how data "travels" inside your application.&amp;nbsp; So a general suggestion is to keep a star and not a snowflaky model, and keep the calculations as tight to your fact table as possible.&lt;/P&gt;</description>
    <pubDate>Sun, 17 Nov 2024 07:53:22 GMT</pubDate>
    <dc:creator>Vegar</dc:creator>
    <dc:date>2024-11-17T07:53:22Z</dc:date>
    <item>
      <title>how to use App Metadata Analyzer to identify what causes AAALR log entry</title>
      <link>https://community.qlik.com/t5/App-Development/how-to-use-App-Metadata-Analyzer-to-identify-what-causes-AAALR/m-p/2492917#M102257</link>
      <description>&lt;P&gt;Hei,&lt;BR /&gt;We have lots of AAALR entries in engine log.&amp;nbsp;&lt;BR /&gt;I know we can use&amp;nbsp;&lt;SPAN&gt;DisableNewRowApplicator=0 to use a different algorithm.&lt;BR /&gt;But I would like to understand what causes the AAALR to appear. If it is related to app design, probably we can try to improve, instead of blindly using&amp;nbsp;DisableNewRowApplicator=0.&lt;BR /&gt;&lt;BR /&gt;Can you advise?&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Susan&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Nov 2024 08:07:47 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/how-to-use-App-Metadata-Analyzer-to-identify-what-causes-AAALR/m-p/2492917#M102257</guid>
      <dc:creator>Huiying</dc:creator>
      <dc:date>2024-11-15T08:07:47Z</dc:date>
    </item>
    <item>
      <title>Re: how to use App Metadata Analyzer to identify what causes AAALR log entry</title>
      <link>https://community.qlik.com/t5/App-Development/how-to-use-App-Metadata-Analyzer-to-identify-what-causes-AAALR/m-p/2493053#M102282</link>
      <description>&lt;P&gt;There are a couple of discussions in this topic already in the community pages, but none who can explicitly explain the AAALR. It might be as an earlier community member &lt;A href="https://community.qlik.com/t5/QlikView-App-Dev/SE-LOG-when-AAALR-6-186927-is-greater-than-1-000000-we-suggest/m-p/934774/highlight/true#M322828" target="_self"&gt;suggests&lt;/A&gt;, sharing the details around AAALR would also reveal core secrets about Qliks engine.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But as far as I understand it can be related to GUI calculations and how data "travels" inside your application.&amp;nbsp; So a general suggestion is to keep a star and not a snowflaky model, and keep the calculations as tight to your fact table as possible.&lt;/P&gt;</description>
      <pubDate>Sun, 17 Nov 2024 07:53:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/how-to-use-App-Metadata-Analyzer-to-identify-what-causes-AAALR/m-p/2493053#M102282</guid>
      <dc:creator>Vegar</dc:creator>
      <dc:date>2024-11-17T07:53:22Z</dc:date>
    </item>
  </channel>
</rss>

