Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Intelligence (Analytics)
Pagebreak+data related issue
kirti1105
I have a report having 4 tables. The data of all suffice in 4-5 pages. But when the data of first table becomes more than one page long, the first page of the report remains blank and is displayed from next page. I have checked all the pagebreaks of header, text element, table n groups in table and all were having auto status except pagebreak inside= avaoid which i purposely set to avoid breaking of a record when data doesn't suffice in a single page.
Find more posts tagged with
Comments
kirti1105
I have a report having 4 tables. The data of all suffice in 4-5 pages. But when the data of first table becomes more than one page long, the first page of the report remains blank and is displayed from next page. I have checked all the pagebreaks of header, text element, table n groups in table and all were having auto status except pagebreak inside= avaoid which i purposely set to avoid breaking of a record when data doesn't suffice in a single page.
mwilliams
Can you recreate this issue with the BIRT Classic Models sample database?
If not, can you attach your design?
kirti1105
Hi Williams,
As i m engaged in other work i'll reproduce that issue later. For now i m attaching the rpt design. Also the screen shots of the same.
Thanks & Regards,
Kirti Wankhade
kirti1105
Sorry yesterday i forgot to attach the file.Also i tried to reproduce the issue using sample database 'Classical models'. But it has no issue like this.
Thanks & Regards,
Kirti Wankhade
mwilliams
Being able to run the report would be best, if you can keep trying to reproduce the error. You don't have to use the sample database, you could put together a flat file of dummy data that looks very similar to the data you're using and create a report using this data.
If not, you might try removing the "avoid" page break within settings one by one to see if a particular one is causing the issue. Do you have this same issue in between tables? Or is this specifically a first page issue?