Share via

bottom line on cascading parameter nuances

db042190 1,516 Reputation points
2021-02-04T17:45:47.517+00:00

hi we run 2014 developer in our dev environment.

i've always been under the impression that with cascading parameters, there's a possibility of a drop down somewhere in the "chain" acting funny. Even if that behavior is by design.

i've always been under the impression also that there is a slick fix that has something to do with perhaps guids and temp tables that guarantees a credible refreshed list on all cascaded params after a change is made to 1 or more of the parameters.

That's great but i have a question before i even go that far.

can someone spell out the behavior i'm referring to? i'm trying to save myself , my peer and my users from going down a road we might not be interested in.

maybe its best to get started by requesting the answer within this context:

  1. the 1st parameter is a customer type. It has 3 available values. it has no defaults. 1 or more values can be chosen.
  2. the 2nd parameter is a customer status. It has 3 available statuses. no defaults. all values are valid with any cust type. 1 or more values can be chosen.
  3. the 3rd parameter is a reason any customer got its current status. there are no defaults. coded generically there are 41 available values and growing. 1 or more values can be chosen. it would be much more manageable if the choices were limited by selected type(s) and status(es).

forgetting how i would code the dependency by the 3rd param on the values chosen for the 1st two, what unexpected behavior might my user see when somebody changes a choice somewhere? It could be important to note that there are 7 params before these 3 and 3 after. none of these other 10 params has any relationship with another param.

SQL Server Reporting Services
SQL Server Reporting Services
A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
2,818 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Joyzhao-MSFT 15,566 Reputation points
    2021-02-05T08:22:42.08+00:00

    Hi @db042190 ,
    Unfortunately I have not seen such "funny" behavior within my development with cascading parameter. Mayby I have not tried with 10 parameters casecading also I did not have complicated third party generated parameter values. So, I am quite sorry here I cannot assist you further. You could screenshot the actual issue or problem that I can replicated in my environment, or you could show us what is the uncomfortable behavior, so we could investigate with you and offer possible help.
    Best Regards,
    Joy

    If the answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.