Vizlib's guidance documentation is your resource guide to making the most of Vizlib products.
This documentation focuses on the Vizlib Container Grid so that the people working with this extension can find useful information to improve performance and succeed with the extension.
We're committed to keeping this documentation up-to-date, ensuring you have access to the latest information as it becomes available.
TABLE OF CONTENTS
Best Practice
- Performance
- The chart uses the Qlik Sense hub engine, and each value will be processed separately. We can find more information in our Best Practices and Performance Optimization article in Qlik Sense.
- Improvements in version v2.11.0 are made to the Snapshot and Context menu. Please read more here: Vizlib Container Grid release version v2.11.0.
- It is recommended not to overfill the page with Vizlib Container Grids. The usual maximum is between four (3) to six (5) single-layer Containers containing no more than three (3) simple visualisations.
Known issues
- There are currently no Known issues
Limitations
- Snapshot the whole Vizlib Container Grid
- Taking a Snapshot of the entire Vizlib Container Grid has a long loading time. The time it takes depends on the complexity of the chart and factors like the user's machine and internet connection.
- Export
- Nested (multi-level) and single-layer Containers don't export (to PDF or Image) as you see them on Qlik. You only see your visualisation(s) within the nested Container(s).
- Exporting nested Containers (to PDF or Image) will only present the Container name and tab content up to two (2) levels deep. If using Nested Containers greater than two (>2) levels deep, then you will only see the visualisation and none of the Container content/names.
- The Vizlib Container Grid cannot export data when added to an embedded sheet, or when a preview is generated.
Tech Understanding
- Snapshot of an individual visualisation
- The Vizlib Container Grid has its own Snapshot method that happens nearly instantly when taking a 'Snapshot' of a specific element within the Vizlib Container Grid. There is no loading indicator or 'colored squares' to indicate a Snapshot has happened as of version v2.11.0. Please read more here: Vizlib Container Grid release version v2.11.0.
- Exporting
- When performing an Export to PDF or Image and using multi-layered containers, the Qlik engine has to render the component as many times as you have nested Containers. Therefore, if an example time of five (5) seconds is taken to print one (1) layer of the Vizlib Container Grid and within your visualisation, you have three (3) layers, then it will take a combined total time of fifteen (15) to twenty (20) seconds to render the component.
- Snapshot of the entire Vizlib Container Grid
- When performing a Snapshot of an entire Vizlib Container Grid the Qlik engine has to render the component as many times as you have visualisations (the Vizlib Container Grid is considered a visualisation in this context). Therefore, if an example time of five (5) seconds is taken to print one (1) visualisation within the Vizlib Container Grid and you have three (3) visualisations, then it will take a combined total time of twenty (20) to twenty-five (25) seconds to render the component.
- Note: This is further increased when taking a Snapshot of the entire Vizlib Container Grid when using nested (multi-layered) Containers
- When performing a Snapshot of an entire Vizlib Container Grid the Qlik engine has to render the component as many times as you have visualisations (the Vizlib Container Grid is considered a visualisation in this context). Therefore, if an example time of five (5) seconds is taken to print one (1) visualisation within the Vizlib Container Grid and you have three (3) visualisations, then it will take a combined total time of twenty (20) to twenty-five (25) seconds to render the component.
- Two containers referencing the same master item
- If using two Vizlib Container Grids within your app and referencing the same Master Item components within multiple Vizlib Container Grids, then making a selection in one Container (i.e. referencing the same nested containers) will also be made within the other Container.