Exporting data as a PDF report is handy in a lot of use cases. Unfortunately there is a limit to how large we can make these. When you try to export a report containing detail pages for more than 1000 features, you'll get a warning.

Error explaining you can't export more than 1000 features in a PDF report

It's pretty heavy for our severs to generate reports that large and going larger than that would not be workable anymore for most personal computers. A report containing detail pages for 1000 features can easily become 300MB for example.

๐Ÿ’ก Note that reports that don't contain detail pages can contain statistics covering more than 1000 features.

The solution: filters

Luckily there's a simple solution: use filters to reduce the number of features or split up the report. We won't cover filters themselves in detail, as you can learn more about filtering here. We will look at some of the handiest filters for PDF reports.

Split up a report using regions

By defining regions on your site you can easily split up your site and your PDF reports into smaller chunks. Just define your regions, filter on one of them and export your PDF report with the Apply filters checkbox turned on.

Focus on a subset of features

By focussing your PDF report on a subset of features you can easily reduce the size of your PDF report. A few common cases are:

  • Filter on specific types of issues. You can create one report focussing on cell-level issues like hotspots and another one covering substring-, panel- or string-level issues.

  • Filter on issues requiring a certain remedial action. You can create a specialised report for issues requiring a field check or for issues that will be taken up in a warranty claim.

  • Filter on issues of a certain severity. You can directly filter on the severity of the anomalies, or use your own rules taking the delta temperatures of the issues into account for example.

๐Ÿ’ก When exporting a report with a certain filter, it might be handy to save the filter you used. It allows you to easily export the same report again and evaluate the same data in the platform.

Did this answer your question?