Reporting services. SQL 2005 SP2

  • I'm suggesting to change behavior of multiselect parameter, when "select all' was checked and parameter page is post back, because of the change in the dependancy parameter.

    For example , there is a multiselect parameter @Employees , that depend on the parameter @Department. Department 'A' was selected In @Department parameter. Based on this selection EmpA1, EmpA2, EmpA3 are shown in the @Employees. And 'Select All' is checked in the @Employees. Change @Department to that Department A and B are selected. Then list in the @Employees contains EmpA1, EmpA2, EmpA3, EmpB1, EmpB2, EmpB3. But "Select All" is now unchecked, because only EmpA1, EmpA2, EmpA3 were resubmitted on post back and only they are selected. I do not think this is a right behavior. When posting back, attention should be paid that "Select All" was the user selection and on the post back, everything should be selected in @Employees again. Also it would be more informative, to show in the text portion of the multiselect parameter words "Select All" or "All", when "Select All" is checked, even though when submitting parameter it should contain all values in the string, which are in the dropdown portion

  • Hello

    a question about multivalue cascadeD parameters.

    I have a parameter PRODUCT (key and descipcion) whose values are

    PRODUCT TABLE

    prodkey description

    === ========

    1 product1

    2 product2

    3 product3

    Each product has one o more subproducts:

    SUBPRODUCT TABLE

    subkey descripcion prodkey

    === ======== =======

    1 sub1prod1 1

    2 sub2prod1 1

    3 sub3prod1 1

    1 sub1prod2 2

    1 sub1prod3 3

    2 sub2prod3 3

    3 sub3prod3 3

    Now, how I build two cascaded parameters (PRODUCT and SUBPRODUCT) with multivalue?

    I mean: if I select all products, then in the second parameter I have duplicate keys, so that it doesn't work.

    Is there a simple way to solve the issue?

    THANKS

    carlo

  • The simple way would be to return a combination of ProdKey and SubKey as your parameter key, you would need both of these anyway when the parameter is passed through to your SQL Query.

    Once inside the SQL Query you of course will need to parse the parameter key value so that you have both values available again.

    Good Luck.

    Nigel West
    UK

  • Thanks, that 's that i'm doing.

    Anyway, it looks to me as a so normal situation (when using cascading parameters) that I was wondering if there's a built-in easier solution to manage it, like the possibility of selecting a combined key...

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply