We just upgraded from Infragistics 9.1 to 9.2. I have a WebDropDown that was working on 9.1 that is no longer firing SelectionChanged server event all the time.
Here is what I discovered when debugging. If I had defaulted the WebDropDown's selected item to the first item in the list, and then click on another item on the list, the selectionChanged server event is not being fired. If I then click back on the first item again, and now click on another item, now the selectionChanged event starts to fire and work from that point on.
Also, if it happened that I didn't default the selected value to the first item, (i.e. any other item was defaulted for selection) then the selectionChanged event is firing correctly. (but of course there are times where you need the first item selected).
Any ideas?
Pam Crissman
Hi Pam,
Thanks for letting us know about the issue. How have you configured postbacks in order to have SelectionChanged fire on the server? Do you set AutoPostBack property, or use AutoPostBackFlags? I suggest to use AutoPostBackFlags for SelectionChanged=On/Async, or ValueChanged=On/Async (but not both at the same time), since the AutoPostBack property has been marked as Obsolete.
How do you select the first item initially ? By setting Items[0].Selected=true, or using SelectedItemIndex =0 in code behind?
Let me know if I can help with something else, if you are still having this issue.
Thank you,
Angel
This is a follow up to my original post - this issue involves selecting the first item returned in the result set - for example if I search for employees with last name "Thomas" and get back 4 matches, if I select the first item (full employee name) in the list the selected value text does not update to show the full employee name, only what I typed. However if I select the second item (employee) in the list, it does update to show the full employee name, then when I go back and select the first item it will update to show the full name. When I databind the result set during the async postback I explicitly set SelectedItemIndex to -1 so that no items are pre-selected as I have no idea what "Thomas" employee the user is looking for - I don't want to make any assumptions. Selecting the first item always updated the display text in the web drop down in 2009.1 but now in 2009.2 SR 2056 it does not.
I too am having a similar problem after upgrading to 2009.2 SR 2056. We use the WebDropDown as a dynamic pick list for search for employees. You start typing an employees last name and it will auto-filter based on employee name pattern matching - what used to happen in 2009.1 when I selected one of the employees returned was that it would set the displayed text of the drop down to the full name that I selected, now in 2009.2 SR 2056 it only shows the text I have typed even though behind the scenes it has actually captured that I selected a particular item. I don't understand why this had to change or if something behind the scenes did not get upgraded when I use the project upgrade utility.
Any insight would be much appreciated.
Respectfully,
Michael A. Jensen
Previously, the SelectionChanged event was fired always, no matter whether the new selection is the same as the old selection. This was updated to fire the event only when there is actual change in the selection. But i guess what you are describing is a little bit different - since in your scenario the new selection is different from the old one. I created a sample WebSite, using the latest Service Release build for 9.2 - 2003, and couldn't reproduce this. Please take a look at my example, and see whether you do it in the following way (it's attached) Maybe i am missing something.
Thanks for the feedback,