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

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 ...

Document ID Service - New Feature in SharePoint

When I explored this new feature of SharePoint in Online (this feature is available in SharePoint 2013 also), I found it interesting because it solved one of the common problems people faced in SharePoint. I will first explain about this feature and I'll cover the problem and the solution in another post. This feature allows Site Collection Admin assign a unique ID to every document in the site collection out of the box. If you recall, there was no out of the box way to assign a unique number to the documents across libraries in a site collection. Yes ID column is unique but only within a library. Document ID column contains a number which is unique across libraries. To start with, let's have a look at a typical document library. This is a familiar view for SP guys. By default, you don't get Document ID column in a library. All Items View To get Document ID column, you need to activate a site collection feature "Document ID Service" as shown below. S...

How to update Person field with multiple values using REST API

Person or Group field in SharePoint is similar to a Lookup field. When you are updating this field using REST API, you need to append "Id" to the name of the column in the body construct. For example, the body construct looks like this: data: { "__metadata": { "type": "SP.Data. ListName ListItem" }, "Title": "First Item", " PeopleField Id": "4" }; The highlighted portions should be replaced by the actual List Name and Column Name. In the above example, the REST call is updating a List item with Title and People columns. How to get the value for user ID ("4" in the above example) needs a separate explanation and that will be my next post! The above example works fine if Person field is configured to accept only one value. If we change the Person field to accept multiple values, how do we pass more than one value in the REST call? Since we normally separate user names with semicolon in peop...

SharePoint

Search This Blog