Qlik Cloud Analytics: Third-party extensions cannot be exported

[Sonja_Bauernfeind]

Third-party extensions cannot be exported in Qlik Cloud Analytics. We suggest using Qlik native visualizations for any reporting use cases instead.

Additional context on the third-party extension restriction:

• Qlik Cloud Analytics uses a different mechanism for printing and exporting content than Qlik Sense Enterprise on Windows.
• In Qlik Cloud Analytics, a reporting service REST API is used to process these requests.
• The export and extract process in Qlik Cloud Analytics runs the visualization code in a microservice. 3rd-party extensions, which include 3rd-party code, have the potential to include malicious code, which can have a material impact on the Qlik Cloud platform as a whole. To mitigate this, Qlik does not support exploring non-native extensions. 

Environments

• Qlik Cloud Analytics

[Alex4579]

I do not understand how there is not any "trusted" third parites. Vizlib integrations are amazing, and we rely heavily on them whithin our Qlik environment. Are there any plans in the future to address this limitation? Or are we forever stuck with the limited and lackluster Qlik Native visualizations..

[steeramp]

I think it's very frustrating to have to tell our customers. “You can't use this feature” or “You have to invest some money to redesign your Dashboards with a less functional and less appealing look and feel.”
This is definitely a misstep for many customers

[Ken_T]

can you clarify what this means - is this referring to the right click export options, for any non-qlik chart type (custom objects) in the hub?

[alex_nerush]

Why just not to make some kind of sandboxed env. to make "microservice" safe even if extensions is 3d party and may include malicious code?