PrintOnFirstPage property not working

[Michael Hilgers]

Hi everyone,

i have a report with a page header. But on the first page of the report, the page header should be hidden. So i switched the property "PrintOnFirstPage" for the PageHeader Section to FALSE.

Now on the first page the PageHeader is emtpy (all child elements have been hidden), but the PageHeader itself is still visible. Why? From my point of view it should be completely hidden too. Or has anyone another point of view? ;)

Regards,
Michael

[Steve]

Hello Michael,

Page headers/footers are not related to the report itself, but are relative to the margins of the report's media, i.e. to the paper or screen, so this is the expected behavior. The space they've taken up would always be preserved no matter whether there is content shown or they are not visible and this behavior cannot be changed.

All the best,
Steve
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.

[Ryan]

I agree with the original post.  PrintOnFirstPage set to false should hide the entire section and shrink the space up, otherwise there really isn't a point to the property if it is going to reserve white space regardless.

[Steve]

Hello Michael,

In the previous post, I've described the current design behavior. However your suggestion makes sense and this is logged in our system for investigation. If we find a feasible way to do it, we would include it in subsequent versions of the product.

Greetings,
Steve
the Telerik team

[Tobias]

Five years are gone but nothing changed! Shame on you, telerik!!!!!!

[Stef]

Hello Tobias,

Page sections occupy the same space on each page, even if they are hidden - Understanding Rendering Behaviors.

There is an approved feature request for having varying page sections per page, which you can vote for in order to raise its priority - ability for report header to reclaim empty space left by conditional formatting. Note that the task involves changes in the core mechanism of the reporting engine and it is not that trivial.


As a workaround, I can suggest you to combine different reports into a single document via ReportBook. This allows you to have different page settings per report - Page Settings, Sizes and Naming.

Regards,
Stef
Telerik