When you're working with Vizlib Heatmap it's important to be clear about what you can and can't do. We've collected together a list of tips for best practice and known issues and listed them here.
TABLE OF CONTENTS
- Let's introduce you - If you're new to Vizlib Heatmap, or looking to find some information, the Introduction page has links to the product resources and knowledge base articles.
- Work with the wizard - Always use the Setup Wizard to start building a heatmap, you can always add expressions or edit data in the property panel once you have the basic version.
- Hit the highlights - Vizlib Heatmap is good to use with smaller, more simple data sets, highlighting values where you select them. For example, you could have a chart displaying helpdesk data with Days and Hours as your dimensions and the number of Calls as your measure. Using large amounts of dimensions and measures isn't really suitable for a heatmap, so if you do need to work with a large dataset it's better to pick another chart.
- There is an alternative - Vizlib Heatmap can be used with alternative dimensions and measures. If you add alternatives, you'll be able to choose the measure you prefer when you're using analysis mode, changing the outcome of the chart for a much more adaptable and varied user experience. If you'd like to add more focus to your chart, look at adding reference lines to help users analyze the chart data.
- Performance - Vizlib Heatmap uses the Qlik Sense hub engine, and each individual value will be processed separately. If you're working with very large amounts of data, this will affect the Qlik Sense engine processing time and performance may become slower. You can find more information in our article on Best Practice and Performance Optimization in Qlik Sense.
Back to Contents
We currently have no known issues reported in connection with Vizlib Heatmap.