Visualizations

Visualizations are used to present the data that is loaded into the app. The selections you make in the app are reflected in all associated visualizations. If you’re new to creating visualizations, review Choosing the right visualization on Qlik Help.

This section summaries the compatibility of these visualizations across embedding frameworks. For support for Insight Advisor, review Insight Advisor compatibility.

Chart types and properties

Native charts

Native charts are those built into the core Qlik Sense experience, and are accessible via the Charts menu in the Qlik Sense authoring experience.

1. These refer to qlik-embed UI types.
2. These IDs are used as the type attribute when creating charts on the fly—both with the capability APIs and with qlik-embed’s analytics/chart UI. They are distinct from the Nebula ID column, which is used for nebula.js direct development. For a full walkthrough, see Create charts on the fly with analytics/chart.
3. See Pivot table in Visualization bundle for a nebula alternative, note that features and capabilities are different to the native chart.
4. See Straight table for a nebula alternative, note that features and capabilities are different to the native chart.
5. Requires iframe="true" to be added to the <qlik-embed ...> tag of the classic/chart object. This is needed when the object requires additional resources on the tenant such as map tiles, or user-uploaded images, which cannot currently be authenticated outside of the iframe mode.
6. Native embedding of this component requires specific page encoding. See UTF-8 character encoding requirement.
7. Chart exploration is not available by default for this chart when presented in this UI type. Enable it by adding preview="true" to the <qlik-embed ...> tag.

Dashboard bundle and visualization bundle charts

These visualizations enhance navigation and selection in your Qlik Sense app, but haven’t yet been promoted to standard objects. This means they may have some limitations compared to the standard objects, such as missing localization, right-to-left support, accessibility support, or may not be supported outside of the Qlik Sense consumption experience.

1. These refer to qlik-embed UI types.
2. Viz on the fly is supported by the capability APIs.
3. Works with analytics/sheet, but not with analytics/chart.
4. When embedding a layout container, all nested charts must support analytics/chart. Charts without analytics/chart support won’t render inside the layout container.

Visualization extensions

Visualization extensions are supported via:

• qlik-embed:
  • classic/app
  • classic/chart, when iframe="true" is added to the <qlik-embed ...> tag.
• Capability APIs
• iFrame embedding APIs.

Monitoring deprecated charts

To track when users encounter deprecated chart types in your apps, use the Deprecated Charts Opened UI event. This event is emitted when deprecated charts are detected as users open or navigate to sheets in the native Qlik experience or when using qlik-embed with the classic/app UI.

This event is available via the Audits API. The event payload includes chart IDs, types, titles, and sheet context, enabling you to:

• Monitor deprecated chart usage across your tenant
• Plan chart migration strategies
• Track deprecation adoption

For a list of the deprecated objects that are detected with the event, see Find deprecated charts on Qlik Help.

UTF-8 character encoding requirement

Certain visualizations require UTF-8 encoding to render correctly when embedded. If your host page doesn’t specify UTF-8 encoding, users see an error message.

This applies to:

• KPI objects with analytics/chart (default iframe=false mode) or analytics/sheet in qlik-embed
• Charts embedded via capability APIs

If users see the following error, the host page lacks proper charset configuration:

To resolve this issue, add the following meta tag to the host page’s <head> section:

<meta charset="utf-8">

If you cannot set UTF-8 encoding, use one of these workarounds:

• qlik-embed: Use classic/chart with iframe="true":

<qlik-embed
  ui="classic/chart"
  app-id="{app-id}"
  object-id="{object-id}"
  iframe="true">
</qlik-embed>

• Capability APIs: Embed your mashup within an iframe on a page that specifies UTF-8 encoding. This isolates your mashup and fulfills the charset requirement.