dragicevic85
-
Posts
6 -
Joined
-
Last visited
Content Type
Profiles
Forum
Events
Featured Visualizations
Knowledge Base
Documentation (PDF Downloads)
Blog
Documentation (Test Area)
Documentation
Dr. Jaspersoft Webinar Series
Downloads
Posts posted by dragicevic85
-
-
I am having a issue with a report i am working on. When I preview it from jasper studio it is working fine (http://prntscr.com/m8aot3). When I call the same report from an Oracle Apex application this happens: http://prntscr.com/m8ap9k.
Everything after the group header gets thrown onto the second page. Why could this be happening? There is nothing in the band properties indicating that the band should start on a new page. -
Fixed the problem by converting the parameters to String.
-
A little more information regarding my report that i just found out by placing the $P{TO_LOCATION} field on my report . First to mention that the parameter class type is java.math.BigDecimal and the value passed to it is NUMBER. So when i pass the value
6859834425575937898450028587793320060 (this is the only value for which this happens.) it gets turned into this format:
6.85983442557593789845002858779332006E+36
Here is an example of a value for which the report works normally (also NUMBER): 235603922374826907291808379469003592882
Any ideas on how to fix this?
-
I just checked the log. No error has been thrown for this particular situation. Also the query works fine, it returns the data.
Still stuck with this problem.
-
My report has 4 parameters that i pass from oracle apex (from_distributor, to_location, date_from, date_to) to jasperreport server .
The report works fine when i pass any number of parameters to it except when i pass a certain value (to_location). On that value it returns a blank report. When i test the report in jasper studio in preview and pass that value it works fine. This happens only for that one value. What could be the reason for this behaviour? I hope my explanation was clear enough.
Report falls apart when invoked from Oracle Apex
in Products
Posted
I don't know what was the problem. I solved it by redoing one of the subreports.