This project has moved and is read-only. For the latest updates, please go here.

Cascading Parameters Not Loading

Oct 24, 2012 at 2:00 AM

Not sure if this is a known issue, but I am having trouble with cascading parameters in CrissCross.  For example, I have a parameter called "Category" and when that is selected, another parameter called "SubCategory" is supposed to dynamically load.  In CrissCross, the SubCategory parameter does not load. 

Oct 24, 2012 at 10:11 AM

Yes, CrissCross can do this, see:

The problem is that the SSRS web service tends to overestimate which parameters are related to each other. So by default CrissCross ignores what the SSRS web service says, and will only treat parameters as related if you tell it (via ExtraConfig.xml). Alternatively, you can tell CrissCross to get dependant parameter info from the web service (set <IgnoreSsrsParameterDependencies> to false in ExtraConfig.xml), but then it might start treating lots of other parameters as being dependant.

Which method you go for will depend on how often your reports make use of dependant parameters.

Oct 24, 2012 at 5:39 PM

Thank you very much.  Still was extremely helpful! 

Since we are editing a single config file that will be used for all reports, what happens when we have one report with year parameter and a dependent month parameter and then have another report with a year parameter and no month parameter.  Will it be looking for the month parameter since we are telling it that year has a dependent parameter?

Oct 24, 2012 at 5:57 PM
Edited Oct 24, 2012 at 6:01 PM

If you are specifying dependant parameters by name in ExtraConfig, then you specify them per report.

The report is identified by its Path, and the parameter within the report by its name.

There is an example here:

This means that if you have several reports with the same dependant parameters, you need to define them in ExtraConfig for each report. On the other hand, it means the problem you highlight above can't happen.

edit: Also, CrissCross caches ExtraConfig once its running, and only reloads it every 40 mins or so. So if you make changes to it, you need to restart the web app - which you can do by recycling the app pool in IIS or by making an innocuous change to the web.config file (e.g. adding a space somewhere).