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. ...
While working with Qlik we can encouter errors or messages that can be a bit cryptic and contain just an error/message code. Very often these codes are followed by a short description. But sometimes either the description is missing or its … to short :) Finally found some free time to compile a list of the error/messages codes, their short and long description. My data source is a few years old so most likely is not complete. But still there are 300+ codes there. ...
The original announcement can be found here Automatiqal CLI is officially entering its Beta phase! You might not be aware but Automatiqal CLI allows Qlik Sense (QSEoW) deployments/administration tasks to be described in YAML/JSON files. Automatiqal CLI supports: multiple authentication methods multiple ways to define variables define onError blocks and a lot more! Please have a look at the introduction video below. More videos will be added soon! Any feedback is greatly appreciated! ...
In one of the previous post we saw how to use web ticket to establish connection with Qlik Sense Engine. And probably for most cases the approach there is enough. But what if our web app have a requirement to communicate with other Qlik service(s) (in addition to the Engine)? For example, we want to list the reload tasks to which the user have access (this information is provided by Qlik Repository Service REST API)? ...
The initial idea was simple … on paper. Spend few days just to prove that its possible. And it was doable. But to achieve it I had to build solid foundation. I’m not going to say what was the initial idea … yet. But will share where it’s “home” will be and will release all the components of the “foundation”. Since there will be multiple components I’ve decided that it’s a good idea to separate them in their own space. ...
This post is long overdue but finally found the time to complete it. Here we’ll have a look how to establish connection (via enigma.js) to Qlik Sense Enterprise on Windows (QSEoW) when hosting an web app outside of Qlik (not as an extension). And more specifically we’ll have a look at what is the authentication work flow. The (very simple) web app will just list the apps that are available for the logged in user. I’ll be using Svelte as web framework (more specifically SvelteKit) but the general work flow should work in the same way with other frameworks as well. ...
Administrating Qlik Sense sometimes means spending a lot of the time in QMC. And sometimes I need to export some of the tables there just to keep the info somewhere else while I’m on a different screen in QMC. Finally sat down to solve this specific issue - Chrome/Edge extension that can export QMC tables to CSV file or copy the content to the clipboard. UI The extension layout is “separated” into two areas: ...
Another interesting feature of enigma.js are interceptors. Interceptors are similar to the mixins functions but they are executed on lower level - request/response level. Request interceptors are invoked right before the request is send to the Engine and response interceptors are invoked right after the response from the Engine is received and before the data is send to the calling function. You can think of the interceptors as “enigma.js middleware”. ...
In the previous post we saw what are enigma.js mixins. I’ve started an repo some time ago (and npm package) where I’ve been adding mixins that I’ve found useful (or mixins that I’ve found boring to write all the time). And want to introduce you to this list. At the moment the repo contains only mixins that are relevant to application/document. (to distinct the mixins methods from the default enigma.js ones all mixin methods, from this package, are having prefix m) ...
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. ...