Skip to main content Skip to footer

Cascading/Nested Parameters in a Report with a Data Model

Background:

Cascading parameters have revolutionized data refinement in business intelligence and analytics. This feature enables users to filter data with multiple criteria, optimizing search efficiency. One key application is within reports containing embedded data sets. This article serves as a guide to create and configure cascading parameters in such reports.

The focus is on a practical scenario: implementing cascading parameters to filter countries and cities. The "Country" parameter acts as the parent, while the "City" parameter serves as the child. This tandem filtering process results in a precisely tailored dataset for analysis.

By following the step-by-step instructions provided here, users can seamlessly implement cascading parameters and grasp their core functionality. This knowledge empowers users to elevate their data analysis by efficiently filtering information, making their reporting workflows more effective.

Steps to Complete:

  1. Create a Report, either RDL or Blank page. Add a data model.

  2. Add two new parameters. In my example, my parameters are named Country and City. Country will be the parent parameter and City is the child of the Country parameter. We will not set any available values yet.

  3. Edit the data model and add parameters that are wired to the parameters you made in step 2. For example, the Parameter name is Country and the value is {@Country}, while the second parameter name is City and the value is {@City}

  4. Add two filters for each of these parameters. On the left side, the value will be from the dataset. On the right, it will be the matching parameter. The middle should show “=” for single selection and "[]" for in if you want multiple values. 

  5. Add a new data model based on Model Entity, and select the same Entity that the data model you selected in step 1 uses. Name it so you know it is the top level parameter that will be working here. I named mine “CountryLookup”.

  6. Create another data model, and once again, select the same data source that the dataset from step 1 belongs to. Name this dataset and save it. I named mine “CityLookup.”

  7. On the parameters, add a parameter with a value that is the parent level parameter from step 3. In my example, my parent level parameter is “Country”, and my child parameter is “City”, therefore the value that I enter on this step is “{@Country}” and I named this parameter “SelectedCountry”.

  8. Add a filter. Select the parent level value on the left, set the comparison to “=” for single and "[]" for multiple, and the item on the right will be the parent parameter you made in step 2.

  9. Return to the parameters you made in step 2. Connect the available values to their corresponding data models. For example, the Country parameter will have the following available values set:

  10. And the City parameter will have the following available values: 

Conclusion:

By adhering to the instructions outlined in this article, users can create and configure cascading parameters within their business intelligence reports. These cascading parameters will enable more refined data filtering capabilities, enhancing the accuracy and effectiveness of data analysis and reporting processes.

Brandon Boribong

Brandon is a Product Consultant for the Wyn Enterprise platform, where he works on technical demonstrations, support, and blog writing. Brandon graduated with a Bachelor's of Science in Computer Information Science and Technology from Temple University and has experience developing websites and apps, as well as client relations as a customer facing liaison. He likes to work on solving complex problems as a team and helping people achieve their goals through the use of technology. When he isn't thinking of problem solving, Brandon enjoys traveling with his wife, and going on scenic nature adventures. Brandon also loves videography and foreign cuisine.