Passing Parameters from URL in ad hoc view



In JasperServer, passing parameters to specific report through URL is working fine 

example: http://<host>:<port>/<context>/flow.html?_flowId=viewReportFlow&reportUnit=/supermart/Details/CustomerDashboard&customerID=4012

where as in adhoc view same scenario is not working.

Please help me.

VV Nagesh Bodapati


nageshit2011's picture
Joined: Jul 22 2013 - 3:04am
Last seen: 5 years 4 months ago

2 Answers:



Please use this for empeding dashboard http://<host>:<port>/<context>/flow.html?_flowId=viewReportFlow&reportUnit=/supermart/Details/CustomerDashboard&hidden_customerID=4012

I hope it will help!

Siva | HCL

sivasubramanian.v's picture
Joined: Sep 20 2013 - 3:49am
Last seen: 6 years 9 months ago

For Dashboards & ireports its working fine. Only problem with adhocview-cross tabs.

Any way thanks for ur reply.

I have one more problem like "jasperserver 5.2 authentication with external DB". i done changes according to reference document but still it is referring jasper db.

nageshit2011 - 6 years 10 months ago

Hi ,any solution for passing parameter to ad-hoc view ? I am doing somewhat same kind work.Need help

snehal_hibare - 6 years 3 weeks ago

Was there ever any resolution on how to pass hidden parameters to ad-hoc views?

shughes - 4 years 7 months ago
Hi, Not sure about dashboards and hidden parameters, but I was struggling pass a parameter into a report I had developed from an Ad Hoc view. I had a filter which I set up in the AdHoc view which I created the report from. This is the solution I found: - export the report (right click>export). - find the file: TopicJRXML in the zip file which downloads. - find the parameter name of the relevant filter. Its in the first few lines of the code. In my case the field displayed as 'record_id'......the parameter name was actually 'record_id4_1' - append the parameter to your URL using the name you found in the Topic file as follows (using my example): ......&record_id4_1=CRM-0000003 That worked for me. I haven't tried anything more complex like multi-selects or ranges, but I think it should work as per the guidance. Its just about finding the correct parameter name. Unfortunately it doesn't tell you when you have the URL wrong, just defaults to the saved version of the report, which I suppose is useful in some ways but not that helpful when trying to get this right. Hope that helps, might point you in the right direction! Thanks Jason
jason.symons's picture
Joined: Mar 30 2016 - 5:03pm
Last seen: 2 years 9 months ago