When you're working with Vizlib Simple KPI it's important to be clear about what you can and can't do. We've collected together some tips on best practice and known issues and limitations and listed them here for you.
TABLE OF CONTENTS
- Let's introduce you - If you're new to Vizlib Simple KPI, 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 steps in the Getting Started article to start building a chart, you can always add or edit data in the property panel once you have the basic version.
- Figure out your formatting - Formatting data for your KPIs can be complicated if you need to meet certain requirements. We've created a formatting reference to help you work out the formatting you want.
- Performance - Vizlib Simple KPI runs using the Qlik Sense hub engine and each individual value is processed separately, which could affect the performance if you're adding multiple objects and master items in a single sheet. 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.
- One MI per layer - If you're using more than one master item in a KPI layer you'll find performance could be affected. It's better to have one KPI object and use multiple layers within the object, though we don't recommend using more than 10 layers per object.
- Layers make (Qlik) Sense - The Qlik Sense hub engine (see above) is better at processing layers than objects, which is another reason for having multiple layers in a single object.
- Expressions - If you're using Qlik Sense expressions, calculation time will increase as the expression becomes more complex.
Recommended Version - For Qlik Sense Releases up to and including February 2019 we recommend using version 1.6.2 of Vizlib Simple KPI.