Problem solved! Apparently if you have any duplicates in your Value
collection the selected index that is maintained through the state
defaults to the first index in that group of duplicates.
So my items correspond to the Box_Id in the table (the unique
identifier in the DB). There are 8 boxes, 1-8. Then I grab a business
related date and fill the Value collection with this, that date
corresponds to something with each box. The dates (which become
values) could all be different or the same, there is no consistency
with the dates. Well boxes 1-6 all had the same recieve date so the
value was the same for all those items. Therefore, if you select
anything within "Index" 0-5 it will default to 0 because that is the
first item in the list with the duplicated date. Same for "Index" 6-7.
So when it is maintaining its state it remembers the selected index,
but won't allow duplicates in the value field. They should provide a
property which allows duplicates in the value field."
Phuff wrote:
Also, I have another DDL on the page that I fill in the same manner and
it doesn't have these issues. I will keep digging.