Layout container: Can you make chart objects and KPIs load faster?
Hello,
In general, I find that the layout container generates its content quite slowly. Can something be done about it - or is it just the way it is?
I have attached a video that shows how slowly a dashboard made with a layout container is generated. As you may notice in the video each sheet has several actions that selects specific values in five different fields that then has an effect on the values generated.
Is this normal behaviour of the layout container? Or can something be done to make it load faster?
I would like it to load a lot faster since many of our users need to see 3-5 versions of this dashboard with different values of the fields whose values are set by actions in each sheet.
Now I have replaced all KPI objects with button objects that as the label makes the calculations that previous was in the KPI objects, and the page actually loads a little faster. The values in the button objects comes up a little faster, but overall it is seems like it is the rendering of the many objects that takes the most time, although many of the button objects only have simple text content (a fee of them must evaluate variables).
I have attached a video that shows the new behaviour. The version of the dashboard with white text in the objects is the one with button objects instead of KPI objects.
the problem is entirely client-side rendering overhead. While button objects are lighter than KPI objects, loading 50+ individual objects - each requiring its own HTML/CSS and it takes time.
so my next question is whether you could use less objects, for instance:
* new table object for each row with hidden headers. You could use background colour of cells with kpis and possibly other cells with transparent background to mimick similar layout while maintaining a lot less objects
* or maybe new text object which has table functionality in it?
cheers
cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.
Using a Qlik pivot table unfortunately does not meet our requirements. One particular issue with the pivot table (and many other objects in Qlik) is that it responds very badly to changes in browser zoom and screen resolution as the layout gets completely ruined. With the KPI object and Button object we can control it much better and actually control what the user sees regardless of browser zoom and screen resolution (unlike with the pivot table as an example).
I am going to go with the current solution where I use the Button object instead of the KPI object for the KPI's.
