Qlik Reporting Service specifications and limitations

Limitations for in-app reporting

General limitations

These limitations apply to the in-app reporting functionality in Qlik Sense. They are relevant for both template creation and configuration of report generation.

• In-app reporting is not available in Qlik Cloud Government.

• In-app reporting is not available for apps published or distributed from Client-Managed Qlik Sense (including multi-cloud deployments) to Qlik Cloud. To use in-app reporting with these apps, migrate the app to Qlik Cloud using the migration tools (see Setting up the Qlik Cloud migration tools), or manually export the app and re-upload it into Qlik Cloud.

• When using a custom font in your app, it is assumed you have the required license to use that font in output from Qlik Sense. To ensure your fonts are licensed, make use of the multiple open-source fonts available in Qlik Sense for styling app content.

  If you have the required licenses for a font that is not available in the default Qlik Sense themes, Create themes with custom fonts to learn about adding the font to a custom theme.

• When using a custom, third-party, and/or proprietary font in your report, it is assumed you have the required license to use that font in output from the Qlik Reporting Service. For optimal print output, it is recommended to use an open-source font.

• When characters that are unsupported in the selected font are used in app content, these characters will be rendered in output with a font in which they are supported. Different behavior might be noticed if a custom font is used.

• If you use a custom theme in your app to define font use (for example, adding a font file directly to the theme), fonts rendered in various outputs might not be the same fonts you have used in your app.

• Shadows applied to chart objects in the app are not shown in the generated report.

• Reporting capabilities, including the Qlik Reporting Service value-add features and subscription reports, are not supported in Direct Query apps.

• The following objects are not supported in report templates:

  • Filter panes

  • Maps

  • Charts with these hypercubes types: Tree, Pivot, or Stacked

• You can nest a maximum of five levels deep in your report template.

• The maximum number of generated images in a report is 1,000.

• A generated report can contain a maximum of 50,000 objects.

• The maximum number of object instances you can add to a report template is 200.

• Hidden and system fields are not visible in the list of fields to use for levels and pages.

• Using a calculated dimension as a level is not supported. Specifically, the following use cases are not supported:

  • Adding a calculated dimension as a master item, adding this master item to a chart, and then using the chart as a level.

  • Adding a calculated dimension expression to a chart, and then using the chart as a level.

  You can, however, include tabular data consisting of calculated dimension columns inside a level.

• When using master dimensions inside a level, you can only use master dimensions with the Single type. Drill-down master dimensions are not supported inside levels.

• When you add column tags that are associated with a Show column if condition set on a chart, the condition must be met when a report generation event using that template is run. Otherwise, report generation fails. To resolve this issue, if a chart using a Show column if condition needs to be added to the report, add the data to the template as a table tag. Report generation will then run successfully even if the condition is not met.

Technical limitations

The following limitations apply to sharing visualizations, with respect to in-app reporting. If these limits are exceeded, your report will fail. If this issue occurs, contact a user with Can edit permission in the app.

The specific limitations are listed below:

• Maximum image size: 4,000 x 4,000 pixels

• Minimum image size: 5 x 5 pixels for charts and 20 x 20 pixels for sheets

Limits and limitations for PixelPerfect reporting

• An Analysis object cannot be added to a PixelPerfect report template. To add an Analysis to the template as an image, convert it to a chart in the app.

Limits and limitations for in-app report configuration

• When one or more cycles are applied, a report task can generate a maximum of 500 unique reports. When no cycles are applied, the report task can generate a maximum of 100 unique reports.

• You can select a maximum of three fields to cycle for a report task.

• The maximum execution time for a report task with a cycle applied is four hours.

• In a Qlik Cloud tenant, a maximum of 100 report tasks can be created by the same user. A user can free up report tasks by deleting existing tasks they created.

• You can add a maximum of 1000 recipients and 1000 groups to the distribution list of an app.

• Report delivery via Microsoft SharePoint distribution folder is not available if the app uses section access.

• External email clients often enforce size limits for email attachments. Check with your SMTP provider to find out what your limit is.

  Reports delivered to cloud storage connectors have no file size limit.

• Report filters are not compatible with Star statements. If an app contains this statement in the script, reports with filters might show unexpected results.

• When configuring a report filter using the Search selection method, certain search methods are not supported. For more information, see Report filter limitations.

• Hidden and system fields are not visible in the list of fields to use in a report filter.

• If an app contains one or more fields configured with the Always one selected value property, you need to configure your report filters so that the filters select exactly one value for each of these fields. These report filters need to be applied to the report task.

  If a filter doesn't contain a value for these fields, or no filters are associated at all to the task, the report task will fail.

Limitations for reporting with Qlik Application Automation

Technical limitations

The following limitations apply to reporting with Qlik Application Automation. If these limits are exceeded, your report will fail. If this issue occurs, contact a user with Can edit permission in the app.

The specific limitations are listed below:

• Maximum number of fields in the selections: 125

• Maximum number of field values in the selections: 150,000 total field values across one or many fields

• Maximum number of alternate states: 125

  Using alternate states for comparative analysis

• Maximum number of patches: 100

  Patches are properties or styling applied in the app. For example: Adding a sort to a table column.

• Maximum number of variables: 1,100

  Using variables in expressions

• Maximum image size: 4,000 x 4,000 pixels

• Minimum image size: 5 x 5 pixels for charts and 20 x 20 pixels for sheets

• Maximum number of pages in a report: 200

Other specifications and limitations

• If you create PDF or PowerPoint reports, the resolution will be 300 DPI.

• External email clients often enforce size limits for email attachments. Check with your SMTP provider to find out what your limit is.

  Reports delivered to cloud storage connectors have no file size limit.

• Portrait layout is not supported for sheets that will be outputted to automations in PowerPoint format. Sheets set to portrait layout will be converted to landscape. However, you can use portrait layout if you are using the Qlik Reporting Service API. For more information about using the API to create reports, see the Developer Portal documentation.

• When using a custom font in your app, it is assumed you have the required license to use that font in output from Qlik Sense. To ensure your fonts are licensed, make use of the multiple open-source fonts available in Qlik Sense for styling app content.

  If you have the required licenses for a font that is not available in the default Qlik Sense themes, Create themes with custom fonts to learn about adding the font to a custom theme.

• When characters that are unsupported in the selected font are used in app content, these characters will be rendered in output with a font in which they are supported. Different behavior might be noticed if a custom font is used.

• If you use a custom theme in your app to define font use (for example, adding a font file directly to the theme), fonts rendered in various outputs might not be the same fonts you have used in your app.

• Shadows applied to chart objects in the app are not shown in the generated report.

• Third-party extensions are not supported.

• Reporting capabilities, including the Qlik Reporting Service value-add features and subscription reports, are not supported in Direct Query apps.

• Analyses cannot be individually added to reports in Qlik Application Automation using Add chart to report. Sheets with analyses can be added to reports with Add sheet to report or Add selection to report.