Skip to content

Latest commit

 

History

History
41 lines (35 loc) · 1.93 KB

corrupted-reports-when-dataset-is-empty.md

File metadata and controls

41 lines (35 loc) · 1.93 KB
title description type page_title slug position tags ticketid res_type
The Reports Are not Rendered or Generated Report Documents are Corrupted When the Data Set Comes Back Empty
Reports Without Data Result in No Page to Display in the Viewer or Designer and Corrupted Report Documents When Exporting
how-to
No Page to Display in the Viewer and Corrupted Report Documents When Exporting
corrupted-reports-when-dataset-is-empty
1520348
kb

Environment

Product Version 15.0.21.224+
Product Progress® Telerik® Reporting

Description

After upgrading to the 15.0.21.224 or higher Reporting version, the reports that don't receive data may not be rendered. In the older versions, the same reports would have the sections that don't display data as header and footer rendered.

Solution

The issue is caused by the change Report rendering now skips the generated blank pages. Use the property Report.SkipBlankPages to control this behavior that we introduced with [R1 2021 SP1]({%slug telerikreporting/upgrade/2021/r1-2021-sp1%}). The property default value is True, which prevents the report from rendering the report sections that don't contain data. In the case when there is no data returned at all, the entire report may not be rendered as explained in the article section [Skip Blank Pages in the Rendered Report]({%slug telerikreporting/designing-reports/rendering-and-paging/understanding-rendering-behaviors%}#skip-blank-pages-in-the-rendered-report).

The solution is setting SkipBlankPages of your Reports to False, which will revert the previous behavior.

See Also

[Understanding Rendering Behaviors]({%slug telerikreporting/designing-reports/rendering-and-paging/understanding-rendering-behaviors%})