"Application performance comes slow down if bigger expression(Number of lines and logic's) used in front end charts.(Every time we need to write those expressions into variables and call variables directly)"
I would dispute that assertion. Large expressions and large amounts of data can perform very well. Poor performance is more likely cause by what's in the expression or how the data is modeled.
"(Every time we need to write those expressions into variables and call variables directly)"
If you mean defining the variables with a leading "=", that can be a bad idea,
rwunderlich for my own professional interest would you be kind enough to expand on
"If you mean defining the variables with a leading "=", that can be a bad idea,"
Is it just the point at which or how they are calculated?
I've always defined variables as sum(blah) (Rather than =sum(blah) ) and then expanded, as it is how I was taught but I've never actually researched why!
I have had a search here and on the cookbook of course but I am obviously not using the correct terms to return an explanation
If you define an expression in the variable with a leading "=" such as "=sum(blah)", the value will be calculated only once, over all data. If the expression needs to be computed over chart rows, then define without the "=" so the calculation is deferred to the chart. So it depends on where the calculation should be done. See The Little Equals Sign
My comment to the poster was more of a guess. I wasn't sure I understood the comment, but was taking a guess at what he was suggesting, In my tuning practice over the past year I've come across examples of people coding KPIs in variables as "=sum(blah)" and then referencing the variable value in a sheet object. I've experienced performance problems with this approach.
what is difference between personal edition and liscensed version...what are the feauture is established in liscensed version of qlik view..let me know as im new to qlik ivew..
