Notable changes in List in SharePoint Online

The moment you create a List in SharePoint Online there are quite a few notable changes which catches our attention. Let me provide a quick list of those changes.

AllItems View

In AllItems View, we don't see ribbons any more. Instead there is a menu which has all the required actions for a List.

Columns can be added right from the view itself. This is really useful considering it minimizes steps to create columns. We can also change the order of column display in the view by simply dragging a column.

What I also noticed is the List view has ajax implemented. If someone adds an item to the list, it automatically refreshes in my screen. I liked this feature.

List Settings

List Settings option is available under "gear icon". It took a while to figure this out. So the options available in gear icon is contextual. If I'm not in a List view, this icon will not show me "List Settings".

Versioning Settings

Now If you enable versioning, it is mandatory to set the number of versions. There is no "unlimited" versioning option.

Apply label to items

Through this new feature, one can define "retention" period for items. The options for the retention is defined by the Organization (tenant) and this can be set at List level or individual item level.

Filter pane

There is a Filter pane which provides a quick filter capabilities to the List view. This is in addition to the filter option available at individual column level.

Item Count

There is an option to show List Item count in AllItems View with a single click. This will also be an useful metric as we don't have to go to Site Contents every time to check item count.

There are some more interesting additions in SPO. I'll try to blog about those features as well.

Comments

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

Restrict Future or Past Date in List

Many a times you will come across a requirement wherein you need to restrict user from entering future or past date in a List or Document Library Date column. Developers are inclined towards writing either event handler or javascript to achieve this. But, hold on! You can achieve this without writing a single line of code. I have a list which stores Employee details like Employee Number, Name and Date of Joining. Here I need to enure that Date of Joining will not accept future date. Navigate to List Settings -> Validation Settings. Here you can enter the formula to restrict future date as shown below. If you change the logical operator, it will restrict past date. Also, you can put message which will be displayed to user. Now, when you try to enter future date and try Save, you will see the validation message. So, next time you have similar requirement, you know where to try first before jumping into coding!

SharePoint

Search This Blog