Skip to main content

Bug: Some Validation formulae does not allow Folder creation

This is a strange issue observed recently. For some of the validation formulae, folder creation does not work. Let me give some examples to reproduce this problem.

If a validation settings is defined for a Library and it uses conditional formula such as IF/AND/OR, it will not allow folder creation!

I have two columns: Date1 and Date2. I want to compare that Date2 should be greater than Date1 and Date2 should be greater than Today's date. The formula looks like this:

=AND([Date2]>[Date1],[Date2]

When I update metadata, the above formula is applied and everything works as expected.

Now the tricky part. Try creating a folder. It shows the validation message set for the above formula! And it will not allow folder creation! Also folder copy via Explorer view is not possible. A message box pops up as "Can't read from the source file or disk".

Similar observation was made with Column level validation. However, in this case folder creation was allowed from UI. But folder copy via Explorer view resulted in the same error.

Another example is for Choice column. I have defined two values: Yes, No. My formula is:

=[My Choice]="Yes"

This also throws folder creation problem.

This is indeed a major bug as we'll not be able to utilize the power of validation and folder creation. If I get any update on this issue or resolution, will update here.

Comments

Popular posts from this blog

How to get SharePoint List or Library GUID via REST

Sometimes, you would need List or Library GUID to use that in some operation. In such cases, how do you get hold of GUID using REST API? There is a straight-forward end point which you can use: /_api/web/lists/getByTitle('ListTitle')/Id This will return the GUID of a List or Library. There is also another approach. However this approach works only if a List or Library contains at least one item. /_api/web/lists/getByTitle('ListTitle')/items This is a familiar end point which we use to fetch items of a List or Library. To get the GUID from the response, you would do: var listIDTemp = response.data.d.results[0].__metadata.id; var listID = listIDTemp.substring(listIDTemp.lastIndexOf("guid") + 5).split('\'')[0]; As you can see, we are doing string operations to fetch GUID from metadata.id. This contains information only if the response has at least one item.

Get User Id using REST or JavaScript Object Model

Sometimes you would need to fetch the User Id based on either Login name or Email id. You would need User Id if you need to assign a user object to a people picker control or People/Group field. How do we get the Id based on Email or Login Name in client side development? We can achieve that using JavaScript Object Model or REST API. Let me share the first example using JavaScript Object Model (JSOM). var context = new SP.ClientContext.get_current(); this.user = context.get_web().ensureUser(loginName or Email); var o = { d: d, user: this.user }; context.load(this.user); context.executeQueryAsync(     Function.createDelegate(o, ensureUserSuccess),     Function.createDelegate(o, Fail) ); The above code fetches User Id for a given Login Name or Email Id. Interestingly, there is no equivalent endpoint available in REST! The Microsoft documentation talk about a endpoint but I could not get it working. So what is the way to get User Id using REST? You have to use the hidd

All about SharePoint List View Styles

Sometimes, there are out of the box features which we tend to ignore and later when we do apply, we are more than happy about the feature which is readily available in SharePoint. One such feature is List View Style. I never thought I would write a post on this. However, whenever I spoke about this with users, people were excited to see the result. That prompted me to write this post. Instead of getting into only theory part, I will basically take use cases where these styles can be applied and also touch up on on some minor limitations with certain style. When you are creating/modifying a List view, you will get an option to select View Style. As shown below, there are 8 options available and Default is always set if you ignore this style. List of View Styles I will take typical Contact List and Announcement List to explian about these styles. Let us go one by one. Default: This view, as name suggest, is the default style in a view. This is one of the widely seen style