Before Unified Interface, we had several customisations in various scripts that executed when an activity was marked as complete. Critical to this functionality was preventDefault() executing on saveMode 58. Since the Unified Interface update, users are greeted with an ugly error which reads "This form can’t be saved due to a custom setting. Error code: 0x83215605". I cannot remove this error nor can I find a way to have preventDefault execute silently as it once did.

I believe this message is redundant as a) it offers no solution to the end user so informing them of it does nothing and b) if a form has a preventDefault() script unintentionally preventing a save (which I assume the message is intended to highlight) it should be up to the customizer to test the customisation fully before committing it to a production solution, and not the system itself to inform users after the fact.

There has been no communication that I could find from Microsoft about why this feature has been changed. I therefore suggest one of two things; either remove the message entirely, or allow customizers to pass in an extra parameter when calling the function that allows for the choice. At the very least please minimize the message so that it appears as a form notification rather than a full screen message.

Thank you for your consideration.