Removing Header Elements After First Natural Page Break

This topic has come up before as a bug, but it was also said to be fixed in version 2.6.2. I am currently using BIRT 3.7.2. 
 
My goal is to display an item on the first page's header while removing it on all pages after. All page breaks are natural and not controlled. The report must be in PDF format. 
 
Attached is a sample I found on this forum that works as is, but breaks if the master page's header height is increased to 1.8 inches or more (at which point the "page1" text repeats on every page). For my project the header is at minimum 2.1 inches. 
 
The OnRender scripts used are: 
<pre class='_prettyXprint _lang-auto _linenums:0'>if( pageNumber > 1 ){
this.getStyle().display = "none";
}</pre>
<pre class='_prettyXprint _lang-auto _linenums:0'>if( pageNumber == 1 ){
this.getStyle().display = "none";
}else{
this.getStyle().display = "block";
}</pre>
 
Please let me know if this is working as intended and if there is a better solution to pursue. 
 
Thanks in advance! 
 
-NINO 
 
Some links for reference: 
 
<a class='bbc_url' href='https://bugs.eclipse.org/bugs/show_bug.cgi?id=347251'>Bug Report</a> 
 
<a class='bbc_url' href='http://www.birt-exchange.org/org/forum/index.php/topic/22406-hiding-some-part-of-the-report-header-on-specific-pages/page__hl__optional header element__fromsearch__1'>Similar Issue1</a> 
 
<a class='bbc_url' href='http://www.birt-exchange.org/org/forum/index.php/topic/22406-hiding-some-part-of-the-report-header-on-specific-pages/page__hl__optional header element__fromsearch__1'>Similar Issue 2</a>

Find more posts tagged with

Comments

mwilliams

Is the issue supposed to happen in the attached report? For me, if I run the attached, the Page 1 header shows in the first page and the > Page 1 header shows in the rest of the pages. This is also the case when I increase the header height to 2.1 inches. I am using PDF output. Is there something I'm missing? Let me know.

TheNINO

This is odd that it would generate differently for me. I've tried this on two machines and two versions of BIRT and all scenarios give the same results.

BIRT 2.6.1 on Helios
BIRT 3.7.2 on Indigo

Is there anything in a working environment that could cause my report to generate improperly? I've attached the valid and invalid PDFs generated. The ErrorHeader.pdf is generated with a 2.1 inch header. The ValidPreview PDF is generated with a 1 inch header and is working as expected.

Thank you Michael for your help on this. If there is any additional information I can give please let me know.

-NINO

mwilliams

I'll try it in 3.7.2. I used 3.7.0 because that's what the design says it was made in.

TheNINO

Haha at this point I'm open to try just about anything. My mind is slowly entering meltdown from all the crazy things I've tried to do in pulling this off and still keep things looking professional.

Thanks again Michael,

-NINO

mwilliams

I see what you're saying. If you run straight to PDF, in 3.7.2, it doesn't work. If you run the report in frameset mode, instead of preview mode, it works as expected. Not sure why they're different. Probably a minor code change between them made it not work in PDF preview. In case you're not sure how to run it in frameset, you can either run it in the viewer and export to PDF, or if you change your preference to use an external browser and run it in PDF, you'll see in the URL that it says "preview". If you change this to "frameset", it'll do the same as exporting to PDF from the viewer. Hope this helps.

TheNINO

Thank you much Michael - this worked well.

-NINO

mwilliams

You're very welcome. I should also have pointed out that the frameset runs separate run and render tasks, rather than the runAndRender task. So, if you end up running reports using java, be sure that you use the separate tasks, rather than the single one. Good luck, and let us know whenever you have questions!