Skip to main content Skip to complementary content

Configuring report generation

You can configure task-based report generation within Qlik Sense. With task-based reporting, centrally administer the generation of reports with multi-recipient output. Task-based report configurations are designed for burst reporting use cases with automated report delivery. Generation can be triggered manually or on a schedule. Report generation is controlled by a number of building blocks, which are listed below.

Report tasks

Report tasks control scheduled report generation by email or to a remote folder. You can also manually run a report task to generate reports immediately. A report task links together the template you have built, as well as your desired report filters. Users from your distribution list are added to the report task individually or as members of groups.

For more information, see Working with report tasks.

Filters

Report filters control the data reduction applied to reports generated from a report task. A report filter is a dynamic entity that can include variables and expressions. Use report filters to employ a bursted reporting use case.

For more information, see Working with report filters.

Distribution list

The distribution list is a collection of all the recipients, and groups of recipients, that you can add to a report task. Before creating any report tasks, you need to define the app's distribution list. This can be specified from an uploaded file or manually in the load script.

For more information, see Creating a distribution list for your report.

Templates

A report template defines the structure of a report. You can create templates in a number of different formats. Tabular report templates are Excel files that are created with the Qlik add-in for Microsoft Excel. PixelPerfect templates can be created directly within Qlik Sense using the embedded PixelPerfect designer.

For more information about report templates, see:

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!