A report that has been working for 5 years........
Yes, I have checked the entire report including Sub Reports to cater for the new Jasper....
Here is the new Error.
Error filling report ../DocTemplates/applus_11.0/DocTemplates/179/179/06337078947940857_RDDoc4490120388298345770.rdd java.lang.ClassCastException java.lang.Boolean cannot be cast to java.lang.Number
Any ideas please.
New Report Error!
-
- Posts: 2392
- Joined: Mon Jul 02, 2012 12:24 am
- Location: Ulaanbaatar, Mongolia
New Report Error!
Cheers,
Mark
_________________
AwareIM 6.0, 8.7, 8.8, 9.0 , MariaDB, Windows 10, Ubuntu Linux. Theme: Default, Browser: Arc
Upcloud, Obsidian....
Mark
_________________
AwareIM 6.0, 8.7, 8.8, 9.0 , MariaDB, Windows 10, Ubuntu Linux. Theme: Default, Browser: Arc
Upcloud, Obsidian....
-
- Posts: 2392
- Joined: Mon Jul 02, 2012 12:24 am
- Location: Ulaanbaatar, Mongolia
Re: New Report Error!
Well, tracked down the offender...
In a SubReport I have this tag...
<<SUM AbsenceApplicationEvent.EventDays WHERE (AbsenceApplicationEvent.ob_Application=AbsenceApplication)>>
This has been working for the last 5 years .... but now it gives the error above.
Have no idea why.
In a SubReport I have this tag...
<<SUM AbsenceApplicationEvent.EventDays WHERE (AbsenceApplicationEvent.ob_Application=AbsenceApplication)>>
This has been working for the last 5 years .... but now it gives the error above.
Have no idea why.
Cheers,
Mark
_________________
AwareIM 6.0, 8.7, 8.8, 9.0 , MariaDB, Windows 10, Ubuntu Linux. Theme: Default, Browser: Arc
Upcloud, Obsidian....
Mark
_________________
AwareIM 6.0, 8.7, 8.8, 9.0 , MariaDB, Windows 10, Ubuntu Linux. Theme: Default, Browser: Arc
Upcloud, Obsidian....
Re: New Report Error!
Hi Mark,
I had the exact same issue, but was in too much of a hurry to fix the report that I didn't troubleshoot it. I ended up removing the sub-report and trying out the new table feature, which got around the issue.
I had the exact same issue, but was in too much of a hurry to fix the report that I didn't troubleshoot it. I ended up removing the sub-report and trying out the new table feature, which got around the issue.
Andrea