When you're working with Vizlib Table, it's important to be clear about what you can and can't do.
We've collected guidelines for best practices and listed any known issues and limitations we've discovered.
TABLE OF CONTENTS
Best Practice
Getting Started
- If you're new to Vizlib Table or looking to find some information, the Introduction page has links to all the product resources and knowledge base articles.
- Work with the wizard - Always use the Setup Wizard to start building a table, you can always add expressions or edit data in the property panel once you have the basic version.
Performance
Vizlib Table runs using the Qlik Sense hub engine, and each value is processed separately, which could affect performance if the table has many values.
We've listed some recommendations to help you manage this risk, and there's also some general advice about improving performance in Qlik Sense here.
- Calculations add up - If you're using calculated dimensions, these will take longer to process than dimensions without calculations.
- Care with colors - Using a highly customized color increases the time and effort the engine needs for processing and can affect performance. Grouping color settings could help you reduce the impact.
- Size matters - It may sound obvious, but larger tables will take more time to load and complete operations if the engine is processing every event.
Formatting
- Use templates - Templates in Vizlib Table help you instantly apply a look and feel, saving you time and effort. You can design your own and save them.
- Mini charts - Mini charts are great to use but can easily become overloaded with objects. We recommend using them in tables with fewer than 1000 rows.
- Wrap up your tooltip - If you're using a tooltip, you can add custom HTML to wrap the text, which is useful for long expressions. Here's a code example:
<textarea cols="30" rows="2" wrap="hard">This is a sample tooltip to demonstrate text wrapping."</textarea>
Limitations
- Context Menu - Right-Click Context Menu does not work in Mashups.
- Export - When exporting Table data to XLS/CSV etc., the totals won't be included in the exported file. This is a Qlik limitation.
- Export to CSV - If an export to a CSV file returns an error, please duplicate the app, re-publish, and attempt the export again.
- Resize / Reorder - Dynamic Resizing & Column reordering in analysis mode are only stored in the session and reset when entered in the app. In the future, storing your configuration in favorites will be possible.
- Using Minicharts in the Vizlib Table - requires a dimension column to accompany the measure column (where your Minicharts are). You can create a fake dimension in the data model and then hide it in the Property Panel.
- Formatted Exports - These export types are completed on the client side (on the User's browser). Therefore, this means if you are exporting the Vizlib Table with many formatting options (i.e. text style and cell color) the time it takes to complete is dependent on (Read Bulletpoints Below). This means one user may export 10,000 rows faster than another based on the below information. Note: in some extreme cases where the Users computer/browser is not optimal, i.e. runs out of memory, then the User's browser may crash or never be able to download the export.
- Browser performance
- Number of Browser Tabs or Computer Applications open
- PC/Laptop performance and/or remaining resources (i.e. RAM/CPU)
- Number of formatting options per cell/row/column
Known Errors
- Selection (Dimensions) - When Enable multi-select or Selections in dimension options are enabled, Vizlib actions for dimensions are unavailable.
- Selection (Measures) - When Enable multi-select or Allow measure selection options are enabled, Vizlib actions for measures are unavailable.
- Mini Chart Set Analysis - In version 3.16.0 of Vizlib Table (and above), Minicharts supports expressions with multiple parts and set analysis in all parts of the expression.
- Dimensions - If one of the dimensions used in the table is an aggregated dimension, the sparklines will not work properly.
- Search - Search functionality in Qlik Sense June 2017 release suffers when two different apps are loaded into one mashup. This is not the case with subsequent versions of Qlik Sense.
- Search functionality has also been affected by a bug in the Qlik API introduced in April 2018 (ID QLIK-88628) and is not working.
- Horizontal Scroll repositions to the left (that is, to the start) after any change (for example, after sorting the last column).
- Fontawesome - If you have issues with Qlik Sense November 2019 font awesome icons, you can include the HTML below to resolve any missing font awesome icons.
<i class="fa fa-users fa-1x" font-family="FontAwesome"></i>