I have 3 dropdowns, the first is a "major category", the second is "minor category", and the third "manufacturer".

 The minor is based on the selection of the major. They are categories of products.

Now, the user can select just the major category, and find all products for all minor categories for that major category.

They can also select a major and a minor category, and view just the products for that major minor.

I have all the sql done for getting the manufacturers of the products based on only the major category or the minor category.

THe problem is that if I have the manufacturer based on the minor category, it won't get populated until the minor is selected.  If I base it on the major category, then it won't get called if the minor changes. 

 I can see that when the webservice is called, the knowncategoryvalues sent to the manufacturer webservice has the Major and the minor ids in them.

 What would it take to set it up so that as soon as the major is selected, it gets sent with no minor, and if the minor is selected, then then it send with both the major and minor.

Any suggestions?

Thanks,

Mike

Hi Mike,

According to your description, I'm afraid isn't quite easy to change the behavior of CascadingDropDownExtender. But you may try an alternative approach as following:

1. Place three dropDownLists in a UpdatePanel

2. Set their AutoPostback property to true

3. Add SelectedIndexChanged event handler for them

4. Fill the third dropDownList in the SelecetdIndexChanged of the first two DropDownLists respectively.

Hope this helps.
 

Thanks for the update.  That is what I'm ending up doing.  Also, the other problem that can't be over come that I can see is the whole Page directive for disabling event validation.  After getting it to work on a page, I wanted to move it to my master page, but because I'm not going to disable event validation for the entire site, I can't place it there.  So I'll go with your method.

What would be ideal I think, would be if the cascadedropdown extender could trigger all children all down the line.  It seems that the "functionality" is there because, when the end ddl gets it's request, it has the value from the parent and grand parent.  Oh well.

 Maybe next release.

Thanks,

Mike

 You can submit a feature request here so that it can be noticed by our product group.