Hi Marc,
Hi Marc,
I believe I've found another instance in which the [Office 365 Update Changes ‘Display Name’ on Required Fields](http://sympmarc.com/2014/01/23/office-365-update-changes-display-name-on-required-fields/) issue is causing a problem, this time on the SPComplexToSimpleDropdown function.
When using this function on a required field, both the new simple dropdown and the hidden complex dropdown get created with the field's name, but without 'Required Field' appended to the end. So if my complex field starts as "Deal Required Field", the two resulting dropdowns have the Title set as "Deal".
Where this becomes a problem is when dealing with multiple browsers. Since the function is smart enough to do nothing if the dropdown isn't complex, the field winds up with an inconsistent name. IE will have the field as "Deal", but Chrome will have it as "Deal Required Field". This is an issue if you later need to refer to this field with jQuery or something similar.
Thanks!
John Riganati
Hi Marc,
I believe I've found another instance in which the [Office 365 Update Changes ‘Display Name’ on Required Fields](http://sympmarc.com/2014/01/23/office-365-update-changes-display-name-on-required-fields/) issue is causing a problem, this time on the SPComplexToSimpleDropdown function.
When using this function on a required field, both the new simple dropdown and the hidden complex dropdown get created with the field's name, but without 'Required Field' appended to the end. So if my complex field starts as "Deal Required Field", the two resulting dropdowns have the Title set as "Deal".
Where this becomes a problem is when dealing with multiple browsers. Since the function is smart enough to do nothing if the dropdown isn't complex, the field winds up with an inconsistent name. IE will have the field as "Deal", but Chrome will have it as "Deal Required Field". This is an issue if you later need to refer to this field with jQuery or something similar.
Thanks!
John Riganati