After upgrading BIRT from version 2.3.2 to 2.6.1, some reports have started producing empty first pages. I've checked the source XML of the rptdesign and the referenced rptlibrary and verified that ALL settings of page break properties are set to "auto". I.e. there are no forced page breaks anywhere in the report definition. The first page contains the master page header/footer items but no data.
Being a relative newbie to BIRT I'm not sure where to go next to solve (or even debug) this problem. My Google-fu turns up some old BIRT bugs (2.1 timeframe) relating to empty first pages but they were resolved long ago.
Can someone suggest how debug this?
First Page
Second Page
I have identified the source of the problem. When this report was
originally designed (long before my time) a grid was used to effect some
padding around the outside of the content. At the top level of the
design (in the body) is a 3x3 grid with skinny top and bottom rows and
left and right columns, with all content going in the center cell.
body
grid
column1 width=2%
column2 width=96%
column3 width=2%
row1 (empty)
row2
table with all report content
row3 (empty)
All the border cells are empty, and if I completely remove the grid and
place the content table in the body directly, there is no initial page
break.
body
table with all report content
So the bug appears to occur if the content, which is larger than a
single output page, is inside a grid. In this case, the normal
suppression of the page break before the first page does not seem to
function.
It's not clear if this is a bug or a design decision, so I have asked
on the Eclipse community forums if this behavior is expected. I will
update this answer when I get a definitive reply.
EDIT: Looks like a BIRT Bug
EDIT: For us, an acceptable workaround is to simply delete the first row in the grid, which consisted of only empty cells anyway. If the too-large section occurs in the (now) first row, the spurious page-break disappears.
This happened for us when we were including svg - images in Birt. Removing them in the XML - document fixed the Problem. Interestingly this only happens with specific svg - images and not with all of them...
Related
I am on Msoft SQL Server Report Builder, v15.0
I have a multi page report that no matter that forces a blank page every 2nd page.
I have searched through the tablix properties, report properties, header & footer properties and have not found a culprit yet.
I fear that there are somehow some hidden pieces that are causing this issue, but I do not know how to be able to see the hidden pieces.
I have opened the .rdl file up in notepad++ and started walking through the code, but I am not certain where I should look at in there that would cause my problem.
It is a 10 column report that is generated from a dataset culled down, but the report has 3 calculated fields in it, including a column which generates a ranking number.
If you know of a explicit piece of code I should search for that would be awesome, but I know that is a needle in a snowpile.....
Found finally what I had done...
my durn body was the same width as the page sheet so it was pushing the margins off and creating a new page.
Here is a good walk through of what I found.....
http://www.keepitsimpleandfast.com/2009/12/export-of-reporting-server-reports-to.html
We're finding that jqgrid locks up sometimes...particularly when using the Row List drop down. The data (XML) does come back from the server, I can see it in the GET, but jqgrid on the page doesn't refresh...then, most times, it locks up completely and the full page must be refreshed. I've found this happens no matter the dataset size (same thing happens with 100 rows as it does with 3000), no matter the browser, and on most of our grids I've tested.
Any hints on what to look for?
Should I be looking into overriding the default refresh that happens when row list is changed? something like is done here with the Refresh button override:
Olegs Answer
and if so, how would I do that???
After going through my Grid configuration, my HTML and such...I found that I had one broken XML element in the response. This broken XML was a bug in MY code, which always happened at exactly 2 MB of XML output. I traced this back to the server XML response, fixed the output, and now that the XML if proper the grid is paging nicely.
So, if you notice this kind of thing happening, first CDATA your XML, then check for any broken XML.
I have use one sub-report in main report with use of jasper Reports. sub-report is print half of is in one page and other half in next page. but i want to print it is in single page. Please help me.
You can set SplitType to equal Prevent in the detail band properties, but that only prevents a band from splitting from page to page, forcing it to begin on the following page of your report. If the output of your sub-report is naturally longer than the page height you have set, then this will just force the sub-report to begin on the following page. I do not think this would be a desirable outcome since in that case the subreport would still populate two separate pages (actually 3 if you include the resulting blank first page).
All that said one solution would be to check off "Ignore Pagination" in your main reports properties. This will ensure that your entire report is viewed as one single page, but this causes problems when printing or PDF'ing.
You are a bit vague in your question, but its also possible that the detail band height is too high. IReport is "pixel perfect" so if the subreport element begins in the middle of the band then that is where it will start. Also if you have title, page header, or column header bands that are not being used, these will result in unwanted white space.
Hope this helps!
There is a property called "isSplitAllowed" in the band tag that should help you.
http://jasperreports.sourceforge.net/schema.reference.html#band
BIRT 3.71v20110905
One of my data fields is a CLOB with html tags. I'm using the Dynamic Text Control in my report. This specifically happens when:
The Dynamic Text Control content type is to HTML or Automatic
in my case since I have html tags in the data. (Problem does not occur if I set the content type to Plain, but then the HTML tags show up in the report output as text.)
and
The total amount of data to be displayed by the control is more than one full page on its own
(without taking into account spacing used by other controls). If the
total amount of data to be displayed by the control is less than one
full page but can't all fit on the current page, it works as expected (meaning it displays what it
can on the current page and wraps the rest correctly onto the next
page.)
Is this a bug in the calculation for the DTC pagination?
Additional notes - I encountered this while trying to use a sample report that inserts a page break as needed between groups for duplex printing. It works great under most circumstances, but not when this DTC pagination issue rears up. ( GroupAlwaysStartsOnOddPage.rptdesign )
Sorry to disappoint, but this is a known issue and has not yet been resolved. At least not in the version of BIRT that Maximo is using.
What I tend to do is break the dynamic text where possible, experiment until I get the largest possible part on one page and put the rest into another dynamic text field.
This is obviously only a work around, but as far as I know there is not much else that you can do.
We ran into this problem with a dynamic text field containing HTML content coming from IBM Maximo long description fields. The report was designed in BIRT 3.7.1 Designer.
We were able to work around the duplication bug by changing the layout from Fixed to Auto. With Auto layout, it is also not necessary to change the Display setting of the field to "inline" (which we previously had to do to allow it to flow between pages without creating an initial page break).
In our case, changing the layout to Auto did not have negative effects on the appearance or geometry of our report.
In VS2010 I have a report, with a table of data that can cause the report to span multiple pages.
Also on this report I have a rectangle that has some contact information for the company the report is for, that I need it to repeat on every page, to the side of the previous table. However this rectangle is not, and cannot be in the header or footer. Is there a way to make an element of a report repeat on every page?
I'm afraid there isn't. You'll have to mimic this by splitting your report into pieces and forcing page breaks after which you display the header again. You can use the List component to do this and group your data to a fixed row height to break to a next page.