How to find prompt selections when report is in Executing state

[kommireddy]

Does anyone know if there's a way to check prompt selections (date range for example) while a report is in executing state? usually, prompt selections can be seen from run history when a report execution gets completed. But I would like to know if we can find prompts passed to report when user is executing it. There should be some audit or content store table which maintains this info, please let me know if anyone knows about it. Thanks.

[charon]

Hi,

im sure its possible to read out the chosen parameters.
Another way just with Report Studio might be, you create a drill through with the execution button which will open a small report in another window, sized very small and contents just the given parameter as displayvalue().
Would this do the trick for you?
regards
charon

[kommireddy]

Thanks for response Charon. Actually I am looking for more of administrative need. When I look at the administration console to check current activities, it shows all reports in different state. I am particularly interested on reports in Execution state. So, for these reports in execution state, only options available are Set Properties, View Run History details and cancel. When you go to View run history details, it shows the status as executing, but under Report options it does not show prompt selections. It is good to have this info, in case if some user is trying to pull huge data (date range), so that we can cancel the report and report to user accordingly. Let me know if there's any way to find this info.

[charon]

hi kommireddy,

alright, wrong attempt by my side then ;)
hm, i dont know if theres a way to read out the used parameters of reports in execution state. but in case you want to monitor the volume of data of your queries,
you can try it with some functionality in FM or even SQL in cognos which will to a rowcount, then deliver the result back.

i have an similar issue right now, some report queries ive build might bring some huge volume of data back, but they works as designed. still, it might bring the server capacity to its limits in case of several users run the report with "bad" parameters.

what im implementin right now is, i limit the result rows in framework manager for all queries in my framework, then modify the messages xml files in cognos for the error message which cognos will deliver in that particular case (2 many rows)...and therefore will inform the end user he has to limit the data more with "beter" parameters.
There are always several solutions to a problem.. ;)
gl and cheerz

charon :P

[kommireddy]

Thanks for the response Charon.

[navissar]

Hi,
Like charon said, there's no built in way to see the selections the user made. However, since the report in executing right now, you can probably trace the SQL/MDX to get the query sent, and deduce the selections from that. It takes some work, but it will probably work.