Hi,
I originally set up a form to use your SPFilterDropdown function on several Lookup columns that allow multiple selections and it worked perfectly. Then I got a requirement to filter those columns based on the value in another Choice column so I switched to SPCascadeDropdowns, which also works perfectly.
In the new configuration using SPCascadeDropdowns, the filtered list of values is slightly different than it was when I used the SPFilterDropdown based on the matching criteria.
My problem is that when users edit an item where a previously saved value from the SPFilterDropdown set is no longer in SPCascadeDropdowns set, the previous value is deleted because its not in the list to pick from.
Is there a way to prevent this from happening? (does it even make sense?)
Thanks!
I originally set up a form to use your SPFilterDropdown function on several Lookup columns that allow multiple selections and it worked perfectly. Then I got a requirement to filter those columns based on the value in another Choice column so I switched to SPCascadeDropdowns, which also works perfectly.
In the new configuration using SPCascadeDropdowns, the filtered list of values is slightly different than it was when I used the SPFilterDropdown based on the matching criteria.
My problem is that when users edit an item where a previously saved value from the SPFilterDropdown set is no longer in SPCascadeDropdowns set, the previous value is deleted because its not in the list to pick from.
Is there a way to prevent this from happening? (does it even make sense?)
Thanks!