This project has moved and is read-only. For the latest updates, please go here.


Cascade Dropdowns Do not work if Fields Are Required


Cascade Dropdown fails in 2013-01 and 2013-02a if the fields involved in the dropdown are specified as Required fields. The workaround is make the fields not required. The code fails to be able to locate the fields in the DOM and set the Select type if the field is required -- search by Title fails as when a field is required in SharePoint 2013 the field Title is set to "This Field is required".
Closed Dec 1, 2014 at 4:54 AM by sympmarc
Fixed in 2014.01


sympmarc wrote Feb 2, 2014 at 3:01 AM

This is a new issue due to an update on Office365. Can you please let me know whether you are on Office365 and if so, what your build version is?
See: to determine your build version.

If you're on SharePoint 2010, I've had reports that the December CU may cause the same issue. If that's the case, can you please post the markup for a select which is required? It'll either be a select or an input, depending on the number of options you have.

See my blog post:

sympmarc wrote Feb 2, 2014 at 3:02 AM

sympmarc wrote Feb 2, 2014 at 3:14 AM

Sorry, one more. It'll look something like this:
    <TD class=ms-formlabel vAlign=top width=190 noWrap>
        <H3 class=ms-standardheader>
            <NOBR>Navigation SubArea<SPAN class=ms-formvalidation title="This is a required field."> *</SPAN></NOBR>
    <TD class=ms-formbody vAlign=top>
        <!-- FieldName="Navigation SubArea"
            <SELECT id=ctl00_m_g_7c7eee5f_b3a1_4523_b1cd_cf1c7cba457f_ctl00_ctl05_ctl01_ctl00_ctl00_ctl04_ctl00_Lookup title="Navigation SubArea" name=ctl00$m$g_7c7eee5f_b3a1_4523_b1cd_cf1c7cba457f$ctl00$ctl05$ctl01$ctl00$ctl00$ctl04$ctl00$Lookup>
                <OPTION selected value=8>Beans</OPTION>
                <OPTION value=9>Herbs</OPTION>
                <OPTION value=10>Tomatoes</OPTION>

earllibby wrote Feb 2, 2014 at 5:27 AM

Yes I am on Office/365 and the version number is

sympmarc wrote Feb 2, 2014 at 12:49 PM

OK, great. I have a fix in place in the next alpha. Watch for it and give it a test for me?

sympmarc wrote Feb 2, 2014 at 12:53 PM

p.s. With Office365, you should get familiar with checking the build number using the method in Cory's post above. As they roll out updates, you're getting them automatically. Some of them have known "problems" you can then search for, like this one.