|
Re: Migrate from BIRT 3.7.0 to BIRT 4.3.0 [message #1078993 is a reply to message #1077265] |
Sat, 03 August 2013 23:14 |
|
Sometimes with bug fixes and changes, things in old reports need to be fixed/changed. The bug fix issue would be something that was set up wrong initially, but BIRT was ignoring the problem, which once fixed, broke the report.
1 - Sounds like you have a column bound to a table that doesn't exist in your dataSet or something
2 - Find where you're using the row._outer._outer expression and make sure there is access to that binding
3 - Somewhere you're using .toString() has a null value being passed to it.
4 - It would appear that you've got a field defined as an integer that has a string value.
If you can attach the report having these errors, I might be able to help you find the problems.
Michael
Developer Evangelist, Silanis
|
|
|
Powered by
FUDForum. Page generated in 0.02875 seconds