I am doing something similar, but my problem is that one of my users is using SPCascadeDropdowns and it's not working with the custom calls.
Basically, I want to put a nicer looking multi-select field to replace the LookUp field (with multiple values allowed). My way to do this is to create a new select with better UI, and call functions like GipAddSelectedItems when the user checks/unchecks items. The out of box fields are hidden, although they are still being used in the background by SharePoint and functions like GipAddSelectedItems. This all works perfectly on its own, but it seems to not trigger something that SPCascadeDropdowns requires -- nothing happens to the 'child' field when I add/remove items in the 'parent' field. The SPCascadeDropdowns functions fine when the custom UI code is removed.. they just don't get along together.
Any ideas? My guess is something isn't triggering.. how does SPCascadeDropdowns keep track of changes to a parent field? Let me know if this needs more clarification.
-Steven
Basically, I want to put a nicer looking multi-select field to replace the LookUp field (with multiple values allowed). My way to do this is to create a new select with better UI, and call functions like GipAddSelectedItems when the user checks/unchecks items. The out of box fields are hidden, although they are still being used in the background by SharePoint and functions like GipAddSelectedItems. This all works perfectly on its own, but it seems to not trigger something that SPCascadeDropdowns requires -- nothing happens to the 'child' field when I add/remove items in the 'parent' field. The SPCascadeDropdowns functions fine when the custom UI code is removed.. they just don't get along together.
Any ideas? My guess is something isn't triggering.. how does SPCascadeDropdowns keep track of changes to a parent field? Let me know if this needs more clarification.
-Steven