SharePoint 2010 distincts between true and TRUE for required field

Today while working with the required field attribute in a list I noticed that SharePoint reacted differently if you write TRUE in upper case. The disitinction is when you try to save a new form and some fields have

required="true"

instead of

required="TRUE"

then the lower case variant is not validated on the second postback. So when you first save the form and there are validation errors that are detected server side then on the second postback the required="true" variant is not validated but the required="TRUE" variant is.

Strange.

Comments

Post a Comment

Popular posts from this blog

System.Net.Http dll version problems

Last few weeks we had problems with referencing the correct System.Net.Http version. This is probably because some components use internally higher versions (.NET Core with System.Net.Http 4.2.0.0) compared to the versions that are available in NuGet. Frequently we got errors like: Could not load file or assembly 'System.Net.Http, Version=4.1.1.2, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) What is the solution.... That is a great questions. But we do not have the satisfying answer yet. What we currently do is the following. - Use in all projects the same System.Net.Http version, currently we use v4.3.3 from nugget - Compile the code and check in the resulting Bin folder what the resulting System.Net.Http version is - Use this version as BindingRedirect in the app.config / web.config like <dependentAssembly>...
Read more

SharePoint Survey Back Button

On Internet I could not find a correct solution for implementing a back button in a survey. After some search I found some near implementations but not an implementation that fully worked. One that inspired me was http://sharepointbender.blogspot.nl/2012/04/creating-back-button-on-sharepoint-2010.html but I found the history.back(-2) not satisfying. I wrote my one version in Javascript that uses the FirstField parameter of the survey to implement a correct behaviour. I hope it makes you happy. In the edit form I added a script link to the code below and i added the following statement spbackButton.init("Name of list"); In an javascript file I included the following code. var spbackButton = (function () { var _prevFieldsArray = new Array(); var _currentStep; var _prevPageStep; function setCookie(c_name,value,exdays) { var exdate=new Date(); exdate.setDate(exdate.getDate() + exdays); var c...
Read more

Azure table storage error: One of the request inputs is not valid

Lately I often work with Azure table storage. However I had to deal with a lot of different "{number}:One of the request inputs is not valid" exceptions. I did not find a collection that related the error number with a fault so I start creating my own collection here. 0:One of the request inputs is not valid. Occured when used characters in my partition key / row key. There are limitations on the characters that you can use. For instance / and \ are not allowed. For the details see https://msdn.microsoft.com/en-us/library/dd179338  section "Characters Disallowed in Key Fields" 2:One of the request inputs is not valid. Occurred when working with Azure batch operations. When you include in one batch two table entities with the same partitionkey and rowkey then you will get this error. Solution: Validate that within one batch there are not multiple the same partition / row keys 8:One of the request inputs is not valid.\ Occurred when working with ...
Read more