Skip to main content
Announcements
Introducing a new Enhanced File Management feature in Qlik Cloud! GET THE DETAILS!

Qlik Tabular Reporting General Troubleshooting and Best Practices

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Frank_S
Support
Support

Qlik Tabular Reporting General Troubleshooting and Best Practices

Last Update:

Aug 27, 2024 12:26:59 PM

Updated By:

Frank_S

Created date:

Jan 11, 2024 2:30:06 PM

This article is designed to provide general and specific troubleshooting tips and solutions for the Qlik Tabular Reporting Solution. For general information about Qlik Tabular Reporting, see Tabular reporting with Qlik Cloud Analytics.

 

A Reporting task fails

If a Tabular Reporting task fails:

  1. Check that you have set up your email SMTP server completely
  2. Ensure the report objects within your report template match the object ID found in your Qlik Cloud application
    • ie: xlexbw (found in app)
    • ie: xlexbw_1 (found in report template but not a 'copy' of the original object xlexbw. This object will not work. The objects in the report template and the Qlik App must match (unless the object is actually added more than once. In this case, an underscore will be added and appended with a number. This nomenclature would then represent a 'valid' object copy)
  3. Check that your filters  are accurately configured. Incomplete or inaccurate filters will cause report delivery to fail
  4. If a filter changes for a recipient, the task will fail. Delete and re-add the recipient with it's new filter value to resolve this. See Considerations when renaming report filters
  5. The recipient import file contains comma's in the Name column (not supported).
  6. Always one selected values in app and other report filter limitations may also cause task errors. To resolve see Report filter limitations and solution Report task: "Failed to send: Could not generate"
  7. Making a public sheet that was used in a tabular report, private causes the report task to fail. (Make sheets public to resolve this problem).

 

How to find specific Report Task Failure information

  • As owner/collaborator, open your app and navigate to 'Qlik Reporting'
  • Hover over the 'sent' error message and note the error message

2024-02-12 07_46_14-SaaS Collaboration meeting EMEA_AMERICA _ Microsoft Teams.png

  • Edit the task by clicking on the ellipsis (three dots) menu and selecting 'Edit'
  • Navigate to the 'Distribute' tab and click on 'View'

2024-02-12 07_46_47-SaaS Collaboration meeting EMEA_AMERICA _ Microsoft Teams.png

  • Note the error message found in the next screen as shown below

2024-02-12 07_47_56-SaaS Collaboration meeting EMEA_AMERICA _ Microsoft Teams.png

 

A Recipient Import File Fails to Import or Reloading Indefinitely

Reload indefinitely.png

  • Check the app's load script for 'Exit Script' statements and remove or comment out the Exit Script. See Exit script help page for example.
  • Any existing exit script will terminate further script execution and cause the reload failure during the recipient file import attempt.
  • If using section access and if section application; is missing from end of section access section, this will cause the recipient import to fail.

 

Setup and configuration errors

If Tabular Reporting fails during the setup or configuration stage, verify that oAuth is configured accurately, see Tabular Reporting OAUTH Error Status 400 resolution.

Notes: Each tenant and manifest file requires its own OAUTH authentication configuration profile

 

NPrinting Report Migration

Not all Qlik Objects which work in Qlik NPrinting work in Qlik Tabular Reporting as well. See Qlik Tabular Reporting: the table Individual column option can't be used for some objects.

 

Tabular Reporting Limitations 

For general Qlik Reporting limitations, see Limitations for tabular reporting

In addition, be aware of: 

  • Microsoft Sensitivity Labels are not supported (help documentation is being updated as per HLP-17139)
  • Conditional reporting is not available
  • Cycles not available (Use pages or levels to emulate cycles)
  • Comma's cannot be used in the Recipient import file/name column. Example: Doe, John
  • Multi-Tenant access for a 'single' MS Excel Add-in is currently not available (Under R&D review)
  • One QS app per Excel Report (multiple apps not supported at this time)
  • Report filter limitations
  • Distribution list limitations

 

Related Information:

Labels (2)
Version history
Last update:
‎2024-08-27 12:26 PM
Updated by: