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".
Comments: 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: http://corypeters.net/2013/07/getting-the-product-version-for-sharepoint-online/ 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: http://sympmarc.com/2014/01/23/office-365-update-changes-display-name-on-required-fields/
Comments: 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: http://corypeters.net/2013/07/getting-the-product-version-for-sharepoint-online/ 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: http://sympmarc.com/2014/01/23/office-365-update-changes-display-name-on-required-fields/