Skip to main content Skip to complementary content

Previewing your reports in the template editor

You can preview your reports while working on them in the template editor. You can preview them in their original report format, or choose an alternative. Preview mode applies report, object, and user filters.

Previewing your reports

Do the following:

  1. In the Qlik NPrinting web console, click Reports on the main menu.
  2. On the Reports screen, select your report.
  3. Click the Edit template button to open the Qlik NPrinting Designer template editor.
  4. Click the Template tab, and then click the Preview button to preview your report.

    It may take several minutes for your preview to load, depending on the size of your report.

    Warning noteIf you try to edit your report in preview mode, your changes will not be saved.
  5. If you would like to edit your report, close the preview window, and format your report in the template editor.
  6. On the Qlik NPrinting template editor menu, click the File tab, and then click Save.
  7. Click the Template tab, and then click the Preview button to preview your updated report.
  8. When you are finished editing, click Save And Close.

Previewing in different output formats

You may want to issue your report in a format that is different from its generating template. For example, you may have an Excel report you want to distribute in both .xlsx and .pdf format. Instead of creating a new publish task and distributing the report to a recipient to see the results in the different format, you can simply preview the report in the alternate format.

Each report type has different output format options:

  • Excel: .xlsx, .xls, .tiff, .pdf, .html
  • Word: .docx, .doc, .html, .pdf
  • PowerPoint: .pptx, .pdf
  • HTML: .html, .htm
  • PixelPerfect: .pdf, .html, .xls, .xlsx, .png, .gif, .jpeg, .tiff

Information noteQlik entity reports cannot be altered in the template editor, and therefore cannot be previewed.

Do the following:

  1. Click the Template tab, and then click the Preview icon drop-down menu to see the choice of output formats valid for your report.
  2. Select the output format you want to preview.

A preview of the report is generated in the format of your choice.

Verifying user filters applied when previewing

When generating a report preview, Qlik NPrinting applies report and object filters. Task filters are not applied, because there is no task involved in a template preview.

User filters are also applied, based on your Qlik NPrinting app connection settings. You should check your connection settings to make sure preview mode is applying the correct user filters.

Do the following:

  1. From the main menu, click the Apps drop-down, and then click Connections.
  2. Select the connection your report is using.
  3. Review your connection settings:
    1. QlikView connections
      • If the Connection requires authentication check box is not selected, the preview process uses the Windows user who is running the Qlik NPrinting Engine Windows service.
      • If the Connection requires authentication check box is selected, but the Apply user section access for reports check box is not, the preview process uses the Identity specified in the connection.
      • If the Connection requires authentication and Apply user section access for reports check boxes are both selected, the preview process uses the Windows domain user. This is the user who is running the Qlik NPrinting Designer.
    2. Qlik Sense connections

      Information noteQlik Sense connections always require authentication.

      • If the Connection requires authentication check box is selected, but the Apply user section access for reports check box is not, the preview process uses the Identity specified in the connection.
      • If the Connection requires authentication and Apply user section access for reports check boxes are both selected, the preview process uses the Windows domain user. This is the user who is running the Qlik NPrinting Designer.

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!