Greetings.

I've been having some issues with parameters that have really puzzled me. Sadly I'm still new to CR and training has been slow to come for me so I've had to delve in without a lot of support.

Dynamic parameters in CR 11 have been giving me some troubles. The key one being that when I add a certain field to the cascading list of parameters, my number o choices at the top of the heap diminishes considerably.

Now, all of the values in the cascading parameter are drawn from the same table. So I would assume that it isn't a matter of poor linking or one table not having the data that others do and so forth.

The parameter itself is one that lets you pick from a main group, three sub groupings and two tests names. The addition is to pick a particular individual who did the test, rather than all of those in the group who took it. The prior report that did not have the participant requirement works fine. But the moment I put in that extra field into the parameter, the choices go from ~30 to ~ 10.

Which seems wrong considering that all of the values in the parameter are from the same table. I'm mystified as to what the issue might be, since cascading parameters aren't deeply involving to make, which means there are few options to tweak to try and figure out what is wrong(as far as I know) and wonder if anyone out there has had this sort of problem crop up before. Any assistance would be deeply appreciated.



Edited by MidnightVulpine - 20 Mar 2009 at 7:06am

Basically, the upper levels of the cascading parameter lose values that showed before. The first selection has four that commonly come up. With participant added in, it goes to 1. The next group down is the one that loses out a lot of them.

It's a bit deeper than that, but I was keeping things simpler for the explanation. The original report, which seems to work fine, has a hierarchy of the following:

Member_group
  Sub_Group_1
    Sub_Group_2
      Sub_Group_3
        Test_Name

The customer likes groupings.

The new report is supposed to select similarly, but add on narrowing out a single person from the members of said group subset. Making a copy of the report and recreating the parameter as above, with the addition of participant ends up with a smaller list of options at the higher levels.

That this isn't a 'known' sort of issue leads me to wonder if its a table issue, but I don't see how it would be, since all of the above values are drawn from the same table. There is no linking issue that could be involved in this in such a cause, could there?

At the bottom of the hierarchy for the combined parameter.

The odd thing to go along with that is that I tried making it a separate parameter, such that there were two of them. So the old one and a second one with Sub_Group_1 then participant. Still got limited sub_group_1 records with just the two friends as a separate cascading parameter.

Just as a test maybe try dropping the Test_Name and replacing it with teh problem person field. Just wondering if it does not like 6 levels deep...