Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Write Table now available in Qlik Cloud Analytics: Read Blog
cancel
Showing results for 
Search instead for 
Did you mean: 
Huiying
Partner - Creator III
Partner - Creator III

how to use App Metadata Analyzer to identify what causes AAALR log entry

Hei,
We have lots of AAALR entries in engine log. 
I know we can use DisableNewRowApplicator=0 to use a different algorithm.
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 DisableNewRowApplicator=0.

Can you advise?

Best regards,
Susan

Labels (2)
1 Solution

Accepted Solutions
Vegar
MVP
MVP

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 suggests, sharing the details around AAALR would also reveal core secrets about Qliks engine. 

But as far as I understand it can be related to GUI calculations and how data "travels" inside your application.  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.

View solution in original post

1 Reply
Vegar
MVP
MVP

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 suggests, sharing the details around AAALR would also reveal core secrets about Qliks engine. 

But as far as I understand it can be related to GUI calculations and how data "travels" inside your application.  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.