March 2018
Beginner to intermediate
514 pages
13h 11m
English
Charts are being visualized, selections are being sent to the Qlik Engine by the user, and everything works brilliantly. In most cases, that's enough. But while Qlik Sense objects or charts are re-rendered and pushed every time the data model recalculates, other non-Qlik objects on the screen, sitting outside of Qlik, do not react.
Sometimes, what you need is a listener, which is basically a background function that fires off when a new data model change occurs, a filter is applied, or a reload occurs. These listeners can then fire functions to possibly connect the Qlik Engine model with other APIs and widgets on the screen.
The way to set up a listener is to bind a listener function to the selectionState() ...
Read now
Unlock full access