|
Re: NPE in birt 4.2.2 [message #1039994 is a reply to message #1038958] |
Fri, 12 April 2013 22:50   |
|
Well, it appears to be an issue with a result set. In HTML does it cut at the same point each time? Is some of the report visible? If so, where does it cut off? That might help you figure out which dataSet it's having issue with. If there is no output, can you try writing out to a text file from each dataSet to see where the report fails?
Michael
Developer Evangelist, Silanis
|
|
|
Re: NPE in birt 4.2.2 [message #1043351 is a reply to message #1039994] |
Wed, 17 April 2013 15:39   |
Juan Holder Messages: 14 Registered: August 2010 |
Junior Member |
|
|
Michael Williams wrote on Fri, 12 April 2013 18:50Well, it appears to be an issue with a result set. In HTML does it cut at the same point each time? Is some of the report visible? If so, where does it cut off? That might help you figure out which dataSet it's having issue with. If there is no output, can you try writing out to a text file from each dataSet to see where the report fails?
Dear Michael,
These reports where ok till we migrated from the 2.5 engine to the 4.2.2 engine.
The HTML output always cuts in the same part or section each time, and it is visible untill it finishes . It is the details section that contains a list of groups, it is the report on itself, I mean de iterable part. In PDF we just get a malformed document.
We see which dataset fails, but we can't see why.
thanks in advance
JH
|
|
|
Re: NPE in birt 4.2.2 [message #1043678 is a reply to message #1043351] |
Thu, 18 April 2013 01:56   |
|
Could you tell me which dataSet fails so that when I look in the above report I know better on where to look for where the problem might be? Thanks.
Michael
Developer Evangelist, Silanis
|
|
|
|
|
|
Re: NPE in birt 4.2.2 [message #1048511 is a reply to message #1045128] |
Wed, 24 April 2013 15:16   |
|
I think I might see an issue. In all of your filters, your outer values are defined by data._outer. The outer element is a list which uses "row". Try changing all of the data._outer values to row._outer. This could explain why it makes it part way down the page before breaking. Let me know.
Michael
Developer Evangelist, Silanis
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02434 seconds