Passing Parameter with Hyperlink Drill Through

Which version of BIRT are you using?
Can you attach a sample report based on Classic Models or a flat file that reproduces the issue?

I am using Version 4.2.2 i will try to make a sample but the first tries i dont got the same problem.. i will also try to reproduce my report on a blank one again and see if the problem occurs again.
What i found out so far if i just add my param.value after the report the value is wrong so usualy the Paramater from hyperlink ist 123-456 but at the end of my report it is 123-%

Thanks for the additional details.
 
A sample the reproduces the issue is going to be the best way for to us to provide assistance.

The thing is if i produce a new report with Classic models the problem do not appear. I basically use this setup in my report but somehow the parameter is lost half way... The Hypsample files are just an example how my report looks like.
The realy weird thing is if i Filter one of the charts by choosing -<"select value"> i can only choose the parameter value that i need. but if i dont choose it the result are also different values. As to be seen in the screenshot.
 
But as mentioned earlier if i just put in a data field at the end of my report with the param.value it returns 500-% instead of 500-3000-1619011

Any clues what it could be?

To clarify it once more
At the start of the same report it gives another Param value than at the end. Screenshots below show the start and the end of the report page. Both fields use param.value
 
 
So somewhere, somehow between all my charts and tables the parameter value is changing somehow and i basically use no scripts in it

Without being able to reproduce the issue or see your original report designs it is hard to determine what is causing this issue.
 
How many report designs are you drilling down to when this happens?
Is it possible to post the expressions you are passing to the value of the parameter in the drill-through?
 
One other I can think to check for is the value you are passing to the parameter could have a special character of some sort in it. This might cause some unexpected behavior.

Thanks Freeman for your replies..
I could not create a sample but I FOUND THE PROBLEM yey finaly
A simple misstake made me spend so much time on it.. In one of my computed Columns i wrote an expresion like:
 
if {BirtComp.like(params[
"Artikelnummer"].value, "X))
else { (params["Artikelnummer"].value == "500-%")
} //you might see the misstake... Changed it to the correct expression and it works.. thanks for your afford JFreeman! I realy appreciate the way this community is working

Thank you for the update and details.
I am glad to hear you resolved the issue.
 
Let us know if you have any additional questions.

Hi Jesse,
 
We have designed two reports, first report have bar chart. Second reports will render the line chart based on first report selection (onclick on bar).
 
Use case:-
 
Whenever user click on bar in chart (first report) it should drill down to second report in separate window (new window). But, it is giving login page instead of report render in window. We are using jsapi to authenticate and render first report in jsp page. 
 
It is working in designer and iHub3 server. But, we are calling application then this is happening..
 
Please find the attached drill configuration file in attachments.
 
 
Thanks,
Srinivas

How are you storing the session for the user on your JSP page after authenticating with JSAPI?
 
It sounds like the session for the user may not be stored properly which is causing it to request authentication again.

Hi Jesee,
 
Thank you for replies. We are not storing user session specific to js api after authentication. 
 
Please find our jsp page in the attachments.
 
Kindly give any sample code to store session after authentication with jsapi.

Hi Jesse,
 
We are authenticating ihub3 server using js api :
 
Sample code :-
<div>actuate.load("dashboard");</div>
<div>actuate.load("viewer");</div>
<div>actuate.load("parameter");</div>
<div>var reqOps = new actuate.RequestOptions( );</div>
<div>reqOps.setRepositoryType(actuate.RequestOptions.REPOSITORY_ENCYCLOPEDIA);</div>
<div>reqOps.setVolume(volume);</div>
<div>actuate.initialize(fTypeServerURL, reqOps, userId, passWd, dashboardOrReportCallBack);</div>
<div> </div>
<div>Anything wrong authentication and storing session?</div>
<div> </div>
<div>Thanks,</div>
<div>Srinivas</div>

What browser you are using?
 
One thing that I have noticed in your JSP page is that there are some typos that could be causing some issues.
For example, the variable you are set for the user id is mistyped when it is set:
<pre class="_prettyXprint _lang-js">
var uerId = '<%=userbean.getUserId()%>';
..
..
actuate.initialize(fTypeServerURL, reqOps, userId, passWd, dashboardOrReportCallBack);
</pre>
After correcting some of these errors and modifying the JSP page for my environment, I am able to drill through successfully in Chrome.

As a quick follow up, I just tested in IE 10, Firefox and Chrome and the drill through is working properly for me in all three browsers.

Hi Jesse,
 
We are using IE 11, Chrome Version 41 and Firefox 36. Whenever we click on first report bar then it is opening new window and asking authentication. if we enter user/password correctly then it is working. But we don't want ask authentication in drill down window.
 
Thanks,
Srinivas

Is drill through happening from a dashboard or a report?
 
Have you corrected the errors in the JSP page, such as setting the userId?

Hi Jessi,
 
We have corrected error in jsp page. We have dashboard and it is internally using report. we have implemented drill down functionality at report level.
 
Thanks
Srinivas

To make sure I am understanding correctly, you are loading a dashboard that has a report gadget which is loading the report with the drill down functionality that is having the issue?

yes Jesse. Dashboard has a report gadget and gadget report has drill down functionality. It has issue while drill down this report.
 
Thanks
Srinivas