Reputation: 292
I have a big bunch of cascading parameters in my rdl report with default value 'All' everywhere. But all children go blank after user changes some parent parameter, and then he has to choose 'All' value from drop-down list for each of child parameters manually. This is pretty annoying staff. How can I force report to fix default 'All' value for child parameters, despite of any changes to parent parameter?
Upvotes: 0
Views: 1474
Reputation: 292
I've found decision for my child parameter go-blank problem. In the Report Parameters dialog just print to the 'non-queried' field default value in quotes. For example, in case of olap data source: print
="[Calendar].[Quarter].&[All]"
instead of:
[Calendar].[Quarter].&[All]
After this Quarter child cascading parameter will not lose it's default value 'All' when user chooses another Year. Nuts!
Upvotes: 2
Reputation: 5243
There is nothing you can do by keeping the default value to "All". That is for only the first time the report is rendered. Once you change the parent parameter, the child value is refreshed and then it starts looking towards "Available values" set.
So, whatever values are coming from the dataset which is the source of Available Values, will be considered to populate the child parameter then. So only way you can still have an "All" still, is to modify the dataset. We could probably help you further if you could share the MDX queries for the parameters, or even you could give it as shot.
Upvotes: 0