Qlik Reporting Service specifications and limitations

• In-app reporting is supported in Qlik Cloud Government and Qlik Cloud Government - DoD. Qlik add-ins for Microsoft Office are supported for developing report templates against apps in Qlik Cloud Government or Qlik Cloud Government - DoD tenants. The add-ins are available for Office 365 Commercial only.

• 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 using the Qlik Analytics Migration Tool, or manually export the app and re-upload it into Qlik Cloud.

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

• 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, see 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.

• 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.

• Custom CSS styling applied to sheets is not included in reports.

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

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

• A report task can generate a maximum of 500 unique reports. This limit is evaluated across all templates added to the task, rather than per template in the task. This limit also applies to all report tasks regardless of whether or not one or mores cycles are applied.

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

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

• In a Qlik Cloud tenant, a maximum of 1000 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. The number of total recipients, whether in groups or not, cannot be higher than 1000.

• 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 email 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.

• You can add up to five report template instances to a report task, including copies of the same template. For example, if you add an Excel template twice to a task, with one .xlsx and one PDF output, this counts as two templates added to the task.

These limitations are relevant for both template creation and configuration of report generation.

The following limitations apply to reporting with Qlik Automate. 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

• 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 email 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, see 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 Automate using Add chart to report. Sheets with analyses can be added to reports with Add sheet to report or Add selection to report.

• Custom CSS styling applied to sheets is not included in reports.

More detailed information about your personal automations is available through Automations in the Analytics activity center. Tenant admins can view consumption metrics on the Home tab of the Administration activity center.