The basic scenario as you describe is do-able.
From you 'Launch' page you make a selection and call a report, based on that selection. This 'parent' report then drills down to a 'child' report. Within the child report you then have the report, plus the same selection box from your first page.
The area to take care is, when making a selection in the child report, that you also carry through the parameters passed from the parent report.
If you explain how you create your launch page, dynamic from a master or focexec, or a static select list, and what you pass over as parameters from the parent to the child, then I can explain in more detail how to get the results you want.
You would have to know what the value would be changed to before the drilldown report is created, as there is no way for additional "input" except by clicking on a drilldown link. The would mean the value has to be hardcoded and you could use multi-drill functionality for each value. If these are variable and can't be hardcoded, your in a tough spot. Otherwise you have to go back to the parent report and click on a link that has the other desired value as a field value somewhere.
In FOCUS since 1991
WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex
Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex
WF Client: 77 on Linux w/Tomcat
There is no rule that says a report cannot have an additional selection in it, and an ability to rerun a report based on a new selection value. It all depends on how you construct the report. Dynamic multi-drill is an option, but there are plenty of others. Passing values from one report to another is a standard ability, so with all these in place it is just a consideration as to how best to achieve the results; with none, or minimal js required.
From the parent report you can pass some values you do not use in the child report, but from that child report you can link a second child report with other parameters inherited from the first parent report. (sound confusing....)
We do this a lot. What we do is display the report. In the upper right corner, we have what we call the "Criteria" button. This button is a written in Java Script.
Here's how the button works. When the user clicks on the button a window opens. The user can then re-focus the report. For example, when our reports run, the user is given a State Summary View across Area (Areas are groups of counties). At this point the user can drill down to an Area. The same report is then shown but as an Area summary across County. If the user wants to change to another Area without going back to the parent report, they can click on the Criteria button and go directly to that Area, a specific County or even to another report. Obviously this works best for static and relatively short lists.
If anyone is interested in more specifics, send me a private message and I can put together a few screen shots and share the code.
In FOCUS since 1985. Prod WF 8.0.08 (z90/Suse Linux) DB (Oracle 11g), Self Serv, Report Caster, WebServer Intel/Linux.
|Powered by Social Strata|