Stand Alone Prompt Page

[cory]

Problem:
One of the reports I'm writing has an incredibly slow prompt page (It has cascading prompts and it takes 30 seconds to refresh after each prompt is chosen). I've lumped all the prompt fields into one query and set 'Use for Parameter Info' to Yes for that query and 'No' for all of the other queries (it's a large report with a lot of page breaks).

Proposed Solution:
I tested the prompt query by itself on a different report and it runs quite quickly when it's not associated with the other queries. So an idea I had was to create a stand alone prompt page that constructs a url with parameters from the select boxes using javascript that opens the other report directly from the server. Has anyone gone down this road? Is it feasible/worth the time? Security holes? Other issues?

[kc9400]

Could you not break the prompts down into seperate queries and maybe have a couple of prompt pages, not sure if that will help with the speed but could be worth a shot.

[cory]

It's difficult to break apart the prompts from the same query because they are cascading prompts that rely on each other (country, state, city). But I haven't tried having multiple prompt pages, maybe I can give that a try.

Thanks.

It's also difficult because my organization does not use frameworks and we do everything via custom SQL and has no intention of changing that anytime soon.

[kc9400]

Yeah same with the way we do ours, we do it using SQL. It can be as much of a pain as it is a convenience.

We do something similar with ours where we have IMT, Country, Location, Site, Building etc.......

[cory]

Well, in case anybody wants to know, I found this article to be very helpful:

http://www.ibm.com/developerworks/data/library/cognos/reporting/advanced_report_design/page583.html

It's three html items that allow for you to use cascading prompts without a page refresh. It worked like a charm for me with the exception that the display and use values have to be the same.