Skip to main content Skip to complementary content

Troubleshooting - Exporting

This section describes the problems that can occur when exporting data or stories in Qlik Sense.

I cannot export all my data

I tried to export data from my visualization, and got one of the following messages:

  • Your exported data is ready for download. Please note that your dataset was too large and has been truncated.
  • You have reached the size limitation of the export process. Please reduce the number of values to export or change the settings.

Possible cause  

The data set in your visualization is too large to export.

Proposed action  

Make selections to limit the data you want to export and then export again.

Anonymous users cannot export app data

I want to let anonymous users export data, for example, export as image/pdf/data for visualizations.

Possible cause  

There is no security rule granting anonymous users the right to export data.

Proposed action  

You can enable export of data for anonymous users by creating a copy of the security rule ExportAppData and modifying the copy to only have resource.HasPrivilege("read") in Conditions. See Security rules installed in Qlik Sense.

I cannot export a visualization as an image

I tried to export a visualization as an image, but the export failed.

Possible cause  

The visualization you want to export is too large. The maximum size an exported image can be is 2,000 by 2,000 pixels.

Proposed action  

In the Image settings dialog, as you export, choose the Custom button and set the image size to 2,000 by 2,000 pixels.

I have blank characters in PDF files

I have blank characters in PDF files that were created when exporting stories with labels in Japanese, Korean, Simplified Chinese, or Traditional Chinese.

Possible cause  

Exporting a story with these languages requires the appropriate font, or else the default Times New Roman font will be used. Times New Roman does not support Japanese, Korean, Simplified Chinese, or Traditional Chinese.

This only applies to text in title or paragraph objects in the story. It does not apply to embedded visualizations.

If ja, ja-JP, ko, ko-KR, zh-CN, zh-TW is declared in the CollationLocale setting for the application in the Data Load Editor, the exporting feature will use the first available font from the following ordered lists to generate the PDF:

CollationLocale language Font stack
Chinese Simplified SimSun, SimHei, FangSong
Chinese Traditional PMingLiU, MingLiU, Microsoft JhengHei, Microsoft JhengHei UI
Japanese Meiryo, Meiryo UI, Yu Gothic, Yu Gothic UI, MS UI Gothic
Korean Malgun Gothic, BatangChe

If a font from the above list is not found, characters in your story requiring a Chinese, Korean or Japanese font will not be printed. There will just be a blank space.

Proposed action  

Install one of the fonts used to export PDF for the language that you are using. You cannot choose the font because the system will only use those in the table in the specified order.

Make sure that you use labels that are the same language that you set in the CollationLocale. If they differ, only common characters will be correctly rendered in the created report.

Right to left languages, like Arabic or Hebrew, are not currently supported on labels.

I exported my table but the totals row is missing

I exported a table from my visualization but the row with the calculation of totals is missing from the exported file.

Possible cause  

Only the actual data contained in the table are being exported.

Proposed action  

Recreate the calculation of totals in the exported file.

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!