Skip to main content

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.

Labels:

Comments

Post a Comment

Popular posts from this blog

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 ...
1 comment
Read more

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...
12 comments
Read more

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.
Post a Comment
Read more