Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I have 3 rows of charts with 3 charts in a row.
I have prev and next button to navigate to different options.
so the 9 charts will change to next 9 charts.
Each chart is having one or two calculated dimensions and one or two expressions.
so i have 9 * 5 = 45 charts.
Which is better, With multiple objects (so many objects for few expressions) or to have only 9 objects instead of 45 and having all the expressions in those 9 charts?
Which is better ? Chart with multiple expressions or Multiple Charts with one or two expressions?
If you are using same expression, you can create a variable and reuse it. It will help you to consume less calc time. Also maximized chart consumes more memory compared to minimize memory, so you can try auto minimize in charts.
In chart properties, under object tab you can see the memory consumption and calc time. This way you can optimize the charts.
Uday
Personally I would seek to get rid of the Calculated Dimensions, quite likely by doing suitable pre-calculations in the load script.
Hi, Uday.
Are you able to use Cycle Groups to reduce the number of charts at all ?
Cheers,
Neil
You can use Qlikview Document Analyzer
Here it is
Document Analyzer - Home - Rob Wunderlich Qlikview Consulting
Hi All,
Thanks for the reply,
I am trying to check the calc time for each object and trying to reduce the complexity of the expression.
I am not using cyclic group. The dimensions has calculated dimensions.
I will try to add those calculated dimension in load script and try it in expressions.
But which is better in all your perspective?
Increasing no. of objects or using same object with different expresssions?
I would recommend using the same object with different expressions.
Uday,
Increasing the object will increase the memory.
Increasing the number of expressions in the chart will increase the calc time.
If expression calc time is too high, it will take more time to show the values in the charts.
If the expression is not resource heavy, you can add more expressions in single chart.
as suggested anything that requires calculation should be avoided from the UI level and should be done at the script level.
If you have too many UI objects then either use Cyclic group for same expressions so that the dimension will change based on the selection of the Field in the Cyclic group.
For similar type of business use you can use containers to carry multiple chart objects together and show based on need/selection of tab.