Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Creating cache for multiple prompt answers in report

Status
Not open for further replies.

26point2

Programmer
Jun 1, 2003
18
US
Hi folks,

We have a 7.2.1 web report that has six possible prompt answers-- one choice for each of the last rolling six months. Rather than have to manually run this report six times every morning (once for each prompt answer) to create the caches, I've created six duplicated schedules (again, one for each prompt answer) and tied each one to a subscription I've set up in web. (I don't believe you can use the same schedule for the same prompt choice, since MSTR will overwrite the previous selection-- so that's why you need to duplicate schedules). Thus, I have six subscriptions that execute each day, so that web users can hit the cache whenever they run this report for any of the prompt choices.

So here's the question-- the report's prompt choices are determined by a filter on the last six months--- so how do I have the six schedules fit these changing prompt choices? The subscription forces me to choose a particular month element, instead of the max or some other function. Is there perhaps a way to get the cache updated without having six schedules? We could continue to manually modiy the subscription each month (next month add a new subscription for the August element, drop February), but I imagine there has to be an easier way.

Thanks,
26point2
 
depending on how large your report is and whether you have non-agg metrics, you might be able to get away with it by running the whole report for the last 6 months, and putting the month attribute on the page-by.

That way it looks like the filtering is the same, and the users can flip thru each of the months fairly quickly. Also you get the benefit of caching one report once instead of 6 times.

My word of caution is that iserver is not too happy with very large reports. If your report is less than 1000 rows per month with less than 10 columns, this approach might work.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top