Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I am successfully using the Capability API's exportImg function (and here) to get a PNG image file for certain charts/sheet objects.
But... exportImg is part of the Capability API, which has not been updated since 2018 (!)
Nebula.js is more recent, qlik-embed even more so.
But neither have that nice exportImg() function (or some equivalent) as far as I understand.
My question is simply:
What is the current best-practice if I want to get a PNG of an chart object?
Looking at the QSEoW and Qlik Sense Cloud clients, they do it in different ways:
I could do something similar to the above, but a pre-baked library that wrap this is of course nice..
Does that exist?
We've had some discussions around this, at the moment the guidance is to leverage https://qlik.dev/embed/reports/qlik-api-export-data/ but please do feel free to create an ideation on this one so we can track interest/ further discuss solutions.
If you have other topics from the capability APIs I'd love to hear those too, I've created a map and feedback will help prioritise the items on it.
Right, for cloud that makes sense. But will that approach work with client-managed too?
My use case is an extension that do object (charts, tables, ..) screen shots when certain conditions are met, with client-managed as the main/initial target. But it would be nice if the extension worked in cloud too, without too much adaptation (some work will of course be needed).
I might end up creating two different extensions, which is fine too.
The reporting API looks nice, but that's cloud only, right?
The pressing challenge right now is that the exportImg function does not seem to support horizontal scrolling (for example in a bar chart, using the mini-chart to scroll the bars left/right).
Which makes me look for options that work on client-managed to begin with, but ideally also in cloud.
Would https://qlik.dev/embed/reports/qlik-api-export-data/ still be the recommended tool for this?
Ah, you're quite right, artefact generation is different in Cloud since it relies on a dedicated service. Indeed two methods are needed for this to work in both places.