Qlik Sense Enterprise. Embedding.

[jonip_78]

Our sister company is thinking of adding a dashboard into their web application and have been thinking of doing it with PowerBI or PowerBI Embedded.

I know the basics of embedding QS visualizations into web page but just basics. Does anone know:

For a web application where user signs in and then the application shows data from their database.

1. Is it possible to embed a dashboard into such an application with Qlik Sense Enterprise and how would it work. Would the dashboard show real time data at all or would that be dependent on Qlik Sense reload tasks?

2. Would it still require us to make reports, data connections etc in Qlik Sense Enterprise for each web application user?

[alex_colombo · Accepted solution]

Hi @jonip_78 yes, it is possible to embed Qlik visualizations in a web application. You have multiple objects for embbeding. Let's assume you are using Qlik Sense Cliente Manage you can use:

• iframe. Embed an entire app, single sheet, single visualization
• Capability APIs. Embed single visualizations
• enigma.js or Engine APIs: read Qlik Sense data (no render capability, you have to use a 3rd party library for render charts)

For Qlik Sense SaaS version you can use:

• qlik-embed. You can embed  an entire app, single sheet, single visualization
• Capability APIs. Embed single visualizations (we reccomend to use qlik-embed)
• enigma.js or Engine APIs: read Qlik Sense data (no render capability, you have to use a 3rd party library for render charts)

About data, when you embed a Qlik app you are dependet on Qlik app data, so the Qlik app has to be reloaded, then you can show updated data into your web app.

About question number 2, it depends, if you choose iframe or Capability APIs, then you have to build visualizations within a Qlik app, otherwise, if you choose enigma.js or Engine API, then you can build your own visualizations using an external library.

[JonnyPoole]

Just to add: the end users would basically just consume the app or parts of the app (sheets) just like any other experience. As the embedded page was rendered, the content would qlik would render after a successful authentication into QLik Sense enterprise through a standard SSO solution  (SAML, OIDC, JWT etc...).  The end user's identity in Qlik determines what they see. You may want to employ section access on the app so each different user sees only the filtered data they are entitled to see. Typically with Qlik you try to use the in RAM data approach as matches performance and scalability very competitively. If the use case is very operational in nature and you need fetch data from the database from second to second, you could try and employ direct query or dynamic views to have the data fetched dynamically from the database. Keep in mind that more 'real time' applications are by nature more expensive in all platforms as there are heightened requirements for performance, stability, concurrency, scalability and data volumes. Just be rational with the approach. No point in hitting the database all the time if that will increase cloud warehouse usage costs, or reduce performance, or best of all, the users only need to see updates every hour or twice a day for example.  In that case, use a 'micro batch' or 'incremental batch' approach to better balance the need. THat means reloading the app using an incremental approach or partial approach a few times per day at low cost/low compute with the benefit of better end user performance. 

[jonip_78]

Thank you!