Portlet not passing Parameter to Drill Through Target report in New Window

[deadsea]

Hello Folks:

I am running into a bizarre issue with a drill through report launched from portlet based main report page in to a new browser window. Issue is as follows:

1) Dashboard consists of a prompt portlet (has tree prompt) and an adjacent portlet that has a chart that is displayed based on the prompt value from prompt portlet
2) Main report has a combination chart with drill definations defined and configured to open the report in new window (via "Open in New Window" property)

Scenario 1: Drill Through Defination set to launch target report in New Window

When I select my prompt value from the tree prompt and submit, my combination chart appears and then I click on my chart to drill through to the target report, and this target report runs/appears but my selected prompt values are not passed from source report to target (report runs because I have set a default prompt value).

Scenario 2:   Drill Through Defination set to launch target report in same window

This scenario works and my target report appears inside the portlet with correct parameters passed from source to target

We are running on 10.2.1 FP3 and also today I checked on our decommisioned C8.4 environment and found that the very same report works fine i.e. drill through launches from source in new window with correct parameters.

Has anyone run into this issue? Any tips on troubleshooting this problem?

Thanks for your time and support.

[deadsea]

A quick update folks.

I recreated a single server environment with 10.2.1 Fp3 + IE 11/Latest Firefox as web browser. Same issue occurs i.e. when using open in new window option the drill through source report does not pass the parameter value, but within the same portlet window it passes the value successfully.

Also, if I do drill through outside of portlets (i.e. in Cognos Viewer) it works perfectly (this is in both environments - existing multi server sandbox environment and a new single server test environment).

BTW, does anyone know how to access the value of parameter within the DOM of the target report that is launched after clicking on the source report?

Thanks!

[bdbits]

I have not had this happen to me, and we have a fair amount of drill-through/up/downs but (nearly?) always open in the same window. Have you contacted support? Maybe you found a bug.

A couple of ideas... Is compatibility mode turned on in IE11? Have you tried say IE10, or an earlier version of Firefox? Not sure it is the browser, but it is one thing to check out.

On the source report's drill-through definition, set it to always show the prompt page. This will bring up the target report's prompt page (even if auto-generated) with the passed values in it before the report runs. If you just want to see the parameters, you can display those on the report with the Param*() functions. I've delved into the underlying DOM on a report before looking for data and such, and it is not for the faint of heart. I would not go there again, it is not worth the effort.

[deadsea]

Hello:

Thanks for responding.

I have not had this happen to me, and we have a fair amount of drill-through/up/downs but (nearly?) always open in the same window. Have you contacted support? Maybe you found a bug.

Unfortunately, I have to use new window because of the way layout is set up. The problem I am having is that I could not reproduce the issue with the samples. I literally made the reports identical, but still could'nt reproduce the issue.Finally, I decided to put the stuff on the backburner for now.

A couple of ideas... Is compatibility mode turned on in IE11? Have you tried say IE10, or an earlier version of Firefox? Not sure it is the browser, but it is one thing to check out.

I have indeed tested with IE 10 & IE 11 (both comp. mode on and off) and FF 32. Same issue.

On the source report's drill-through definition, set it to always show the prompt page. This will bring up the target report's prompt page (even if auto-generated) with the passed values in it before the report runs.

I re-checked on this, but prompt page appears without values when doing this.

If you just want to see the parameters, you can display those on the report with the Param*() functions.

I do display the prompt values on the target report, but it appear that values are passed as NULL.

I've delved into the underlying DOM on a report before looking for data and such, and it is not for the faint of heart. I would not go there again, it is not worth the effort.

Yes I did examine the DOM and I could see that my param name as well as its use and display value were correctly encoded within the "window.oCVpagelet<long alph num ID>CDrvCanvas.envParms" call.

I have put this issue on the back burner for now and hopefully will have some time soon to work on this issue again. In the mean time I am hoping if someone runs into this, they could perhaps post any tidbits that may help uncover any oversight on my part.

Thanks!