MicrosoftHi sahilbaid
The branching functionality in Microsoft Lists has been a huge improvement for our team — thank you for that!
However, I’ve run into a challenge: when using branching to skip over certain fields, especially those marked as required, the form still enforces those requirements based on the underlying SharePoint list schema. This means that even if a field is hidden due to branching, the form won’t submit unless that field is filled in — which can be confusing for users.
It seems like the form logic is tightly coupled with the list schema, and changes to field requirements in the form are affecting the list itself. Is there any plan to decouple form behavior from list-level validation, or allow conditional required fields based purely on form logic?
Would love to hear your thoughts or if there’s a recommended workaround!
Thanks again for all the great updates.
Couldn't agree more, there are several list forms I would love to use branching on but I can't because of the mandatory input field requirement. It's not an issue with Microsoft Forms, so I don't know why it is an issue with Sharepoint list forms. Even if the decoupling or the conditional requirement would be complicated task to achieve from the developer's perspective, giving the option for a default value of the mandatory inputs when branching could be an easy fix (for instance, "not applicable" for free text columns, or one of the choices for choice columns, etc.), so we can still hide the question from the users and satisfy the list schema input requirement at the same time.
