Wrong page_break with hide details report

Hi,

I created a report with groups and hide details rows for PDF output. It is working well at Eclipse preview tab, but it does not work at View Report Tool. Neither with View Report as PDF nor View Report as HTML the page_break appears at wrong places. My report needs to have only one page as PDF, but appears with 6. The details rows were hidden, and the group rows were in right place, but there are is a big white space at the page botton.

I think that render task is considering hidden details to calculate the size of the report and the place of the page_break.

Thanks in advanced.

Elvys

Find more posts tagged with

Comments

mwilliams

Hi Elvys,

What version of BIRT are you using? Can you recreate this issue with the sample database?

elvysb

Hi,

I used BIRT 2.3.0, 2.3.1 and 2.5.

I will create a report with the sample database.

Thanks.

Elvys

mwilliams

Elvys,

Sounds good. Let me know when you have it done.

elvysb

Hello,

This sample_report is working at Eclipse preview tab (it uses less than one html page). But at View Report Tool the report uses 3 pages.

If I export this report to PDF or PS, it uses the same 3 pages of View Report Tool.

Thanks,

Elvys

mwilliams

Elvys,

Do you ever display the detail row?

elvysb

Hi mwilliams,

In my report, I need to display some details rows and to hide others.

In this sample report, I hid all rows to show the wrong pagination.

Is it clear ?

Thanks,

Elvys

mwilliams

Elvys,<br />
<br />
Yes, I see what you're talking about. This is definitely a bug. I thought this was a bug in an older version that had been fixed. If you're not setting a specific page break interval, you can select the table and go to the page break section of the property editor and put in 0 for the page break interval. This should work to get around the issue for now. Please log this bug for this at <a class='bbc_url' href='http://www.eclipse.org/birt/phoenix/reportabug.php'>BIRT: Reporting Bugs and Requesting Enhancements</a>. Also, if you don't mind, put any bug information in here for future reference. Thanks.