R:
The "Gip" functions all service the multi-select "dropdown", and that is absolutely supported in SPCascadeDropdowns. The way this all works is that the form loads as it normally does, and then the script takes over to filter the data that's already there. In order for things to work properly on submit, I use the existing functions that drive the GIP because they manipulate a bunch of JavaScript variables under the covers that are needed for the submit to work.
You're using the latest version of SPServices, which is as efficient as I've been able to make things. I'm not saying that it's perfect, but in every version I manage to get some performance improvement. It may be that with your mix of content, the inefficiencies are showing more than for others.
The other thing to consider here is that this all runs on the client side. For that reason, you need to understand the machine parameters and understand that a slow machine will really matter.
M.
The "Gip" functions all service the multi-select "dropdown", and that is absolutely supported in SPCascadeDropdowns. The way this all works is that the form loads as it normally does, and then the script takes over to filter the data that's already there. In order for things to work properly on submit, I use the existing functions that drive the GIP because they manipulate a bunch of JavaScript variables under the covers that are needed for the submit to work.
You're using the latest version of SPServices, which is as efficient as I've been able to make things. I'm not saying that it's perfect, but in every version I manage to get some performance improvement. It may be that with your mix of content, the inefficiencies are showing more than for others.
The other thing to consider here is that this all runs on the client side. For that reason, you need to understand the machine parameters and understand that a slow machine will really matter.
M.
