[Solved] WPF ReportViewer: Initial rendering shows only 1 page, but clicking Preview renders all pages after Telerik Reporting upgrade

1 Answer 23 Views
Report Viewer - WPF
Minita
Top achievements
Rank 1
Minita asked on 25 Sep 2026, 07:38 AM

Hi Telerik Support,

We recently upgraded our application from an older Telerik Reporting version to Telerik Reporting 20.2.26.812 (2026 Q3), and we are experiencing an issue with the WPF ReportViewer.

Environment:

  • .NET Framework 4.7.2
  • WPF application
  • Telerik Reporting: 20.2.26.812
  • Telerik ReportViewer.Wpf: 20.2.26.812
  • Telerik.UI.for.Wpf.AllControls.Xaml: 2026.3.812
  • Previous Telerik Reporting version: 14.0.20.115

The report is a code-based report and has multiple pages. The first page contains patient information, followed by several additional pages/subreports.

The report is generated using an InstanceReportSource.

RefreshReport() is not called anywhere.

Problem

Before the Telerik upgrade, the report rendered correctly on the first load.

After the upgrade:

  1. We click Generate Report.
  2. The ReportViewer initially shows only 1 page, and the page is almost empty/incomplete.
  3. The report should actually contain 4–6 pages, depending on the selected content.
  4. If we click the Preview button in the ReportViewer's report parameter area, the report is processed again and all pages are rendered correctly.

We would like the report to render all pages correctly on the first load, without requiring the user to click Preview.

 

What would you recommend checking to determine why the second processing triggered by Preview produces the correct result while the initial processing does not?

The same report and application logic worked correctly before the Telerik upgrade, so we would prefer to identify the Telerik compatibility/configuration issue rather than modify the report logic unnecessarily.

Any guidance on what logs, assembly versions, or report settings you need from us would also be appreciated (As this is a healthcare application, I won't be able to share code or any sensitive information).

Thanks.

1 Answer, 1 is accepted

Sort by
0
Dimitar
Telerik team
answered on 29 Sep 2026, 03:18 PM

Hi Minita,

Thank you for the provided information about the issue!

Given the description of the issue, it may be due to the ReportSource object used by the report viewer not being automatically updated. After a new object is assigned, please try calling the RefreshReport() method. For example:

            var reportSource = new Telerik.Reporting.InstanceReportSource();
;           reportSouce.ReportDocument = new Report1();
            this.reportViewer1.ReportSource = reportSource;
            this.reportViewer1.RefreshReport();

If this does not resolve the problem, please check whether the report being used has report parameters, and whether their values are as expected at the time of the viewer report source being updated.

If you have ensured both that the report viewer is refreshed and the parameters are correct, but the issue persists, please try reproducing it with our demo project shipped with the installation of the product - C:\Program Files (x86)\Progress\Telerik Reporting 2026 Q3\Examples\CSharp\.NET Framework\WpfIntegrationDemo.

Then, send the updated project with the reproducible issue, so that I can debug it locally and suggest a solution.

I hope that the suggested fixes will help!

Regards,
Dimitar
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Tags
Report Viewer - WPF
Asked by
Minita
Top achievements
Rank 1
Answers by
Dimitar
Telerik team
Share this question
or