nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cascading Parameter Group based on parameterized DataSet

Tubal

Is this possible?

I need to create a dataset based on a report parameter, and then base the cascading parameter group on this created dataset.

The first parameter determines which database tables the dataset is created from.

Then the cascading parameter group would be based on the data that the first parameter returns.

The problem is that the dataset won't be created until you pass the first report parameter, so when you run the report and the parameter page comes up, the cascading group doesn't have any data to create from.

Maybe there's something I can do in the validate script of the first parameter to run/refresh the dataset so I can use that data in the secondary datasets?

Thanks,

Phil

Find more posts tagged with

Comments

lnix

Hi Phil,

How is the first parameter going to be passed in? Will the user have to specify it or is it something the report can pull (like a user name or something)?

Best Regards,
Lindsay Nix | Customer Support Engineer | Actuate Corporation

Tubal

<blockquote class='ipsBlockquote' data-author="'lnix'" data-cid="93012" data-time="1325270291" data-date="30 December 2011 - 11:38 AM">
Hi Phil, 
 
How is the first parameter going to be passed in? Will the user have to specify it or is it something the report can pull (like a user name or something)? 
 
Best Regards, 
Lindsay Nix | Customer Support Engineer | Actuate Corporation </blockquote>
 
It would be a parameter the user passes at runtime. 
 
What I have is a stock report. We have multiple stock tables. So they select the stock table they want to use based on a report parameter, I pass the report parameter to the query, and get my dataset. So far so good. 
 
Then I want the user to be able to drill down based on cascading parameters. 
 
I can have them manually enter their filters, but it would be much more convenient and efficient if they could select them from existing data in the table. 
 
Thanks.

lnix

Hi Phil,

This could get really complicated. There isn't a way to do this on one report parameter window without writing a customer parameter requestor page. So, that's the first option.

The other option is to split this out into two reports. The parent report would have the first parameter to get the parent dataset and then it would call the child report that would contain the cascading parameters. This could be done by loading a basic parent report with a drill down hyperlink on it to call the child report.