If I view each subreport individually, i don't see any blank pages with the data, however if i view the subreports via the master page, i get a blank page with each page of data
in the beginning i noticed this trend due to the margins and i have explicitly set the master page's margin to 0 all around yet am still seeing this problem
any help would be much appreciated!
17 Answers, 1 is accepted


if you have resolved the problem,please let me kwno how to rectify this.
This KB article should point you in the right direction: Telerik Reporting renders blank pages.
Best wishes,
Steve
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.

It seems there was a problem with our server.
Try reloading the page.
I get the same error when trying to open a ticket. Can you send me that information by email? I'm getting blank pages for all even pages on reports that have at least 1 subreport in them and I have a long overdue projected pending due to this situation.
Hope you can give me a quick response. Thanks
We're aware of the issue and working to fix it. As to your issue - the pages are not actually blank. Rather there is some content that cannot fit on the current page and is carried over to the next page. There are several cases when this happens:
- Report Width is greater than than the available page space (Page Width - Left Margin - Right Margin).
- There is a sub-report, which contains a report that is too wide, and while at design-time that is not obvious, at run-time it might cause the carry over to occur.
- There is a report item with boundaries going out to the right from its parent section.
To see which items are causing the problem, simply change their background to a different, more contrasting color and run the report in the WinForms viewer or export it to PDF. The rendered report will immediately give you a clue about the items which are at fault. Then simply try making the report items smaller until the "blank" pages disappear or decrease the report width. We would advise creating the items so that they do not touch other items, section ends, etc., because the processing engine might produce unexpected results. Always leave a little space (a couple of pixels/points) around report items to prevent unexpected behavior.
Blank pages at the beginning of the HTML report can appear, because the DetailSection has its KeepTogether property set to true and the HTML rendering engine attempts to render it on a single page (it is later that it "realizes" that this is impossible). Since the first page contains the ReportHeader, the rendering engine tries to render the detail on the second page, which has more available space. In light of this, try setting the KeepTogether property of the DetailSection to false and/or delete the ReportHeader section of the report, if you do not need it.
All the best,
Steve
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.

I have done all your suggestions and my detail section continues to show up on the 2nd page, not the first page.
My report contains a PageHeader Section, GroupHeader Section, Detail Section, GroupFooter Section and PageFooter section. The GroupHeader, Detail and GroupFooter Sections all have the KeepTogether property set to false. The Detail Section contains a subreport, and the subreport only contains a Detail Section, and it has its KeepTogether property set to false. I have enough data to show in the report to create a 2 page report. When shown in the ReportViewer on the web page, the reports shows up in 3 pages. The first page contains only the PageHeader, GroupHeader, GroupFooter and PageFooter sections. The 2nd page contains all sections, and shows all of the detail data. The 3rd page contains only the PageHeader, GroupHeader, GroupFooter and PageFooter sections. When I print this report, it prints correctly. The detail section shows up on the first page, and breaks when page is full and the remaining data shows up on the 2nd page.
Any tips that you can provide other than what you have already suggested to fix this issue??
Thanks!
Are you using Web ReportViewer? I would assume so, as the printing basically exports to pdf and shows you the print prompt.
If you take a look at the "Design considerations for HTML rendering" help article, you would notice that sections cannot have KeepTogether=false, due to the fact that html is not a page oriented format, each report section is rendered as a separate HTML table and when you combine those two you basically end up with subreport that has KeepTogether=true and might not fit on the first page.
Have you tried coloring your sections/items to better troubleshoot what is going on?
All the best,
Steve
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.

I am using the Telerik Report Viewer, the latest version.
I did color my detail section different than the other sections and it doesn't show in the report viewer for page 1 or page 3.
So because it defaults to KeepTogether = True, does this mean that whenever the detail section data will exceed one page, the whole sections will not be displayed on page 1 nor the last page? This is the behavior that I am seeing. If only have enough data for the detail section that will print on 1 page, then when it is shown in the report viewer I correctly only have 1 page of data shown, but if I have multiple pages of data that will be printed, then I have 3 pages shown in the viewer, and page 2 is the only with detail because it does not split it?
Am I understanding this behavior correctly?
Thanks.
"So because it defaults to KeepTogether = True, does this mean that whenever the detail section data will exceed one page, the whole sections will not be displayed on page 1 nor the last page?"
It means that the data in the section would not be displayed on the current page, whenever there is enough space to render it on subsequent page, without having to split the content of the section. Only when the content is far bigger to be rendered on a single page (there is no way to get squished on subsequent pages either), then it would be fitted on the first one and the rest cut off to the next page.
Sincerely yours,
Steve
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.

So here is what I tried. I removed the subreport, and put the information from it into the detail section of the main report. Now when I view the report in the viewer I see the detail exactly like it will be printed, i.e. page breaks and data on each page, which is what I wanted. The one thing I do not like about this solution is that I have to include the info that is displayed in the PageHeader section in each record of the detail so that when I bind the report to my datatable all the info is available to the report. Please correct me if there is another way to do this that is more efficient.
So if you use a subreport in the detail section of the main report and the amount of data contained in the subreport will exceed more than 1 page when printing, in the viewer it will not show the detail data in page 1. All of the data will be shown in page 2, because it will not split the detail section correctly due to the rendering. Do I understand this correctly?
Thanks.
We are not sure on your scenario and namely what is it that you need to include in the pageheader depending on the detail data?
As for the HTML rendering extension - yes this is correct. The number of the page is not relevant, it could happen on any page, not just the first one.
Best wishes,
Steve
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.

The report shows the contents of a shopping cart for customer. The PageHeader section contains info for the Customer, i.e. Name, Customer Number, Business Name and Warehouse Number. The detail section shows Product, Quantity, List Price, Customer Price and Product Description.
So the datarow in the datatable that is bound to the report looks like this:
CustName
CustNum
BusinessName
WhseNum
Product
Qty
ListPrice
CustPrice
ProductDesc
The first 4 columns are redundant data since I only need these once for each customer not on each detail record. Is there anyway to do this better?
Thanks!
Page Header/Footer sections do not relate to data rendered in the report. To create table like header for the details, you can create additional group without group criteria (unbound group). In header section of this group you can place table header cells. The report definition outline will look similar to this:
groupOrderHeaderSection (PageBreak=Before)
groupDetailsHeaderSection (PrintOnEveryPage=true)
Details
groupDetailsFooterSection (Visible=false)
groupOrderFooterSection
I've attached an example (data is retrieved from AdventureWorks) to demonstrate the idea.
Greetings,
Steve
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.

Are you have a example but with files .Trdx? So i´m working with Telerik designer and I have the same problem, please
Thanks
Reagards
You can find attached a sample report in .trdx format that uses the AdventureWorks database.
All the best,
Elian
the Telerik team
Telerik Reporting Q1 2013 available for download with impressive new visualizations. Download today from your account.

Hi,
i have created a report with RTF template using XML Publisher. when i run the report in pdf format then its showing blank page as the first page followed by the actual report content.
i have already gone through solution given under "Problem: Telerik Reporting renders blank pages" blog but did not find it applicable to my report issue.
please share if any suggestions.
Best Regards,
Please check my post in your forum thread on the same topic.
I will appreciate it if we continue the discussion in one of both threads, allowing us to keep a better track on the exchanged information.
Thank you for your understanding.
Regards,
Stef
Telerik
Hello Paul,
I suggest checking out the Remove Blank Pages from PrintPreview - Telerik Reporting KB article for approaches to removing blank pages from the document.