how to debug what parameters are passed to a sub report?

If I run sub reports on their own, they work. If I call them from a main report, passing in the same parameters, I get zero values.

Is there any possible way to see what parameters either the main report is passing to each sub report, or, even better, to see what parameters the sub report is using in its queries?

I notice that report studio has no log4j.properties anywhere in its installation dirs.

john.v.little's picture
Joined: Aug 28 2014 - 3:29am
Last seen: 8 years 8 months ago

3 Answers:

I assume what you are asking is to see the values of  parameters being passed from main to sub report.

You can simply display your paramters in the sub report title section and run the main report again to see what values are being passed to the sub report. Make sure to add some markers around the displayed values such as

"parm 1 ="+$P(parm1}+";"

to help you tell whether there's any leading or trailing spaces/white charatcters in the parm that will crew up your select where condition in the query.

tchen's picture
121571
Joined: Feb 27 2008 - 7:33am
Last seen: 1 day 9 hours ago

I was hoping to enable some kind of debug logging with the parameters in it, but this works also. Thanks!

john.v.little - 8 years 9 months ago

Hi there -- 

Try this, maybe it helps:

1 - Create the main report and a parameter.
 
2 - Open the sub report and create a parameter with the same set the same data type.
 
3 - Now map the parameters.  
 
4 - Return to main report, and right-click on sub report, or just select it.  
 
5 - Open its Properties panel.
 
6 - Look for the Parameters button or configuration (near the bottom).
 
7 - Click the Add button from the pop up.
 
8 - Or, you can use the "Copy From Master" button; from there you should be able to select the parameters that you want to pass.
 
H Mendoza's picture
1835
Joined: Feb 20 2013 - 11:39am
Last seen: 3 years 11 months ago

You can print out information to the console as described in How to get Jaspersoft Studio logging output from within scriptlet.

Or you probably want to enable FINE-level logging for the specific class you're interested in. See Configuring Apache Commons Logging and Log4J in Jaspersoft Studio and https://community.jaspersoft.com/questions/841628/it-possible-log-genera... for an example.

kkumlien's picture
9079
Joined: Jan 22 2015 - 4:36am
Last seen: 2 months 4 weeks ago
Feedback
randomness