Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Team,
I'm encountering an issue when trying to render Vizlib objects from my Qlik Sense application within a React application using the @qlik/embed-web-components library.
My current implementation looks like this:
<qlik-embed object-id="[YOUR_VIZLIB_OBJECT_ID]" app-id="[YOUR_APP_ID]" ui="classic/chart" ></qlik-embed>
Problem: When using ui="classic/chart", the embedded component displays a spinner icon indefinitely instead of the expected Vizlib object.
Attempts to Resolve: I have also tried the following ui types and properties, but none have successfully rendered the Vizlib object:
ui = "analytics/chart"
ui = "object"
Adding iframe ="true" property
Expected Behavior: I expect the Vizlib object to render correctly within the <qlik-embed> component in my React application.
Could anyone please advise on the correct configuration or potential solutions for rendering Vizlib objects using @qlik/embed-web-components? Are there any specific considerations for Vizlib extensions when embedding them this way?
Thank you in advance for your help!
This usually comes down to a support/compatibility gap rather than something wrong in your React code.
qlik-embed-web only supports standard Qlik visualizations and charts built on Nebula, and most third-party extensions (including Vizlib) don’t render correctly through it because they rely on the classic client / Capability APIs. In that setup the object either never initializes or shows up as a blank container.
Typical workarounds people use:
Embed the sheet or object via a full iframe to the Qlik hub/app instead of qlik-embed-web, so Vizlib runs in the native client.
Or build a classic mashup using the Capability APIs where Vizlib is officially supported, and then load that mashup into your React app.
So, in short: what you’re seeing is expected with Vizlib + qlik-embed-web at the moment; you’d need to change the embedding approach to get those objects to render.