Hello,
Could you please help me clarify something I have encountered?
I have noticed that when a field is both disabled and required, the required field validation does not seem to apply when saving the form. Only fields that are not disabled are validated as required.
The fields on the form are disabled and required using:
fd.field('Field1').disabled = true;
fd.field('Field1').required = true;
Could you please clarify whether this is expected behavior, meaning I should look for a workaround, or whether it might be a bug?
The last update I received was on 22.10.2026.
Thank you!
Dear @ana.gheorghita,
SharePoint form and SharePoint fields? Or public web form?
Dear @ana.gheorghita,
Sorry for the long wait - confirmed with the dev team that it's by design. You can still check these fields with field validators though, do you need help setting it up?
Hello @Nikita_Kurguzov,
I just assumed, based on the documentation that I consulted, that a field can be disabled and still be set as required, for example for fields that are automatically populated with values on form render, or any time during the user’s interaction with the form. These fields would be disabled because, we don't want users to edit their values, as the information they contain needs to remain accurate.
Also, it got confusing because the field looks required on the form, even though disabled at the same time.
However, if you confirm that this is by design, could you please help me with setting field validators for the situation I described. If, for some reason fields remain empty I would like to alert the user that the form can’t be saved for now because of empty required values and ask them to try later .
Should I perform this validation inside spBeforeSave, or is there another recommended way to handle this?
Thank you in advance!
Dear @ana.gheorghita,
It used to be this way, but we've since added rules to hide/disable fields based on conditions, and these rules are working the same way regardless if field is required or not, thus the change has been made to make disabled fields not required. It's also not clear what user can do to correct required field missing info if the field is disabled.
There are pros and cons to either change we make here, but we've decided that it's better to ignore field requirements for disabled fields.
You can use field validators instead, they are added directly to a field with JS - Work with SharePoint form fields in JavaScript — Plumsail SharePoint Forms Documentation
Thank you for your assistance @Nikita_Kurguzov!
I understand the reasoning behind the changes that were made.
In my particular situation, where fields contain employee information or other data that can’t always be validated if entered manually, I would prefer to ask the user to try again later, while addressing the issue, rather than letting them fill in the missing values themselves.
I'll try using field validators as you suggested.
Thanks again for your help!
Dear @ana.gheorghita,
If you have any issues - post here, we'll help adjust the code!