Hey Marc, as I commented on your blog post, I encountered one bug with this new function. I have a custom list with several columns that appear in this order on the form:
- Title (single line of text)
- State (lookup to "States" list)
- City (lookup to "Cities" list)
- Partner State (lookup to "States" list)
- Partner City (lookup to "Cities" list)
I'm using SPCascadeDropdowns for State > City as well as for Partner State > Partner City. I'm also using the new SPComplexToSimpleDropdown on all four columns. All are required columns. For some reason the Partner State and Partner City columns don't
pass validation. I'm using jQuery 1.3.2 as that is what's deployed to this particular environment. I haven't had a chance to try reproducing it in another environment, but I'll certainly try as soon as I can and let you know if I can reproduce the issue.
One other request for this new function: could you provide an option to create a blank default value for the simple dropdown that is rendered?
Consider when you create a Choice column with the drop-down control. You can make it a required field, and set it's default value to be blank. That way the end-user is forced to click the drop-down and select a value.
With a lookup column of less than 20 items, the default value is always the first item returned by the lookup; it's not set to be a blank value. If this field is required, the user could submit the form without ever having to make a selection or even look
at the options in the simple dropdown.
SPComplexToSimpleDropdown creates the same simple dropdown; the default value is the first item in the array of items listed on the complex <input> element. It would be nice to prepend a blank <option> to the beginning of the simple dropdown
so that if a user tries to submit the form without making a selection, the complex <input> only sees a blank value instead of being defaulted to the first item. It'd be just as if the user never typed anything into the complex dropdown <input>.