Skip to main content Skip to complementary content

Generating On-Demand reports in Qlik Sense

On-Demand reports are created using the On-Demand reporting button.

When you create an On-Demand report, the report is added to the report creation queue on the Qlik NPrinting Server. Once a report is complete, it is stored in the Qlik NPrinting repository. Reports can be accessed from the Qlik NPrinting window in QlikView AccessPoint until deleted. Reports and reports in queue are automatically deleted from the Qlik NPrinting Server after 30 days. Failed reports are deleted after 6 days.

To enable On-Demand reporting in Qlik Sense, see: Installing Qlik Sense On-Demand reporting control.

Information noteOn-Demand requests only work with reports based on a single connection. MultiDoc reports are not supported.

Documentation for the Qlik Sense On-Demand reporting control

For documentation describing the On-Demand reporting control in Qlik Sense, including limitations and other considerations, see On-Demand reporting control.


  • Users must be logged into Qlik Sense via NTML (Windows) authentication in order to generate reports or create reporting buttons.

Accepting the Qlik NPrinting web console certificate

The default installation certificate for Qlik NPrinting web console may be registered as invalid by your browser. If your browser registers the Qlik NPrinting web console certificate as invalid, you must accept the certificate before you can use On-Demand in QlikView AccessPoint or Qlik Sense.

Information note

If you switch to a different browser or clear your browser’s cache, you will have to re-accept the Qlik NPrinting certificate. On-Demand works in Chrome, Firefox, and Explorer. It does not run in Microsoft Edge, because the certificates will not download.

Do the following:

  1. Open the Qlik NPrinting web console.
  2. Depending on your browser, do one of the following:
    • Choose to continue to the Qlik NPrinting web console.
    • Add a security exception and continue to the Qlik NPrinting web console.
  3. Log into your Qlik NPrinting web console.

You can now use Qlik NPrintingOn-Demand using this browser.

Creating an On-Demand reporting button

You can create an On-Demand reporting button on the sheet you are editing.

  1. From the assets panel, under Custom objects > Dashboard bundle drag On-demand reporting to the sheet.
  2. In the property panel, under NPrinting Connection > NPrinting server URL, set the server connection. The URL must end with /.

    For example: https://<server name>:4993/

  3. Under NPrinting App, select the Qlik NPrinting app that contains the report template.
  4. Under NPrinting connection, select the Qlik NPrinting connection.

    As the default, the list only shows Qlik NPrinting connections to the Qlik Sense app you are working in. You can use the App/Connection filter toggle to display connections not associated with the current Qlik Sense app.

  5. Under Report Configuration > Choose Report, select the report you want to connect to the button.
  6. In Default Export Format, select a default export format.
  7. Under Appearances > Button Label, set the button label. For example: Generate report.

You have now created an On-Demand reporting button.

Generating a report

You can generate a report that is filtered according to the current selections in the Qlik Sense app. You need to be in analysis mode.

Information noteYou can only filter on fields that are included in the Qlik NPrinting report template, or the report will fail. It is not possible to filter on selections using an expression.
  1. Click on the button that you created.

    The Export dialog opens.

  2. There are two buttons to choose from:
    1. Quick Report: generates a single report with the default output format.

    2. New Report: choose from a list of reports that have been made available to you. You can also choose the output format.

  3. When the report is generated a download button is activated. Click the Download button to download the report.

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!