1 minute read
As is often the case recently, inspiration for this post came from a thread over at the MSDN SharePoint – Design and Customization forum. In this particular thread, I suggested using the PreSaveAction (see my post entitled Validation on SharePoint Forms – Part Four for details on how this works) and some script to do some validation on a form. The reason in this case was that the form was very long (due to a large number of columns) and users weren’t seeing the error messages higher up on the page when they clicked "OK".
From a usability point of view Sharepoint is implementing a pretty bad default way of validating forms here. Well, just gotta work my way around it.
Thanks for the help.
I think you always need to put SharePoint through the 80/20 mental test. The way the out of the box forms work is absolutely fine for [at least] 80% of the use cases. IMHO, Microsoft is interested in selling seats to the development community and keeping that ecosystem up and running in a healthy way. That’s where the other 20% comes in. The other thing to consider is that these default forms are pretty amazing in that they just work, and they work regardless what types of columns you throw at them.