When I was writing the code for qlBuilder reload command I knew I’ll have to come back to it, at some point, and refactor the part that is displaying the reload progress. The plan was to separate this functionality as a separate module or even a package so it can be used elsewhere as well. ...
You know it already but enigma.js is the JavaScript wrapper around the Qlik’s Engine API. If you are building a mashup/web app or some sort of automation that require Engine communication you’ll have to use Engine API and here enigma.js is your friend. Just to mention that JavaScript is not the only “flavor” of Enigma. You can find enigma for Go and .NET But in this post I want to introduce you to one very cool (but not very popular) functionality that Enigma provides - mixins. ...
In Qlikview if there is a need to test/debug something developers are just creating some textboxes or straight/pivot tables right next to the dashboard (or in another sheet). In Qlik Sense it’s bit more tricky because the free space is kinda limited and if the need to check is on top of already fixed dashboard then some free space need to be made which involve some re-arrangement which I’m not big fan of. ...
The Technology team asked me these days is it possible to provide them with live data who are the active qlikview users and which documents are accessed. This info is visible in the Management console but since our environment is a cluster with 3 QV servers if you want to check the active users you need to constantly click around to get the info. So I’ve ended making small c# console app that uses the Management API to extract this info in csv or json format and store the data in file. So now I can schedule the execution for the app and give Technology the link to the output file. ...