Follow Us:
It’s been awhile but I am back to continue on my SharePoint Basics series for SharePoint. Let’s see where we are:
Back in Part 2, I touched on SharePoint Views briefly in the context of creating content. In today’s post I want to go a lot deeper with views and show you how to work with them which will help any SharePoint user work more effectively and efficiently. Again, if you have a good handle on what views are and just need the how, you can skip down to the Steps for SharePoint 2010 or Steps for SharePoint 2013 headings below.
As I mentioned before, SharePoint content is stored in lists or libraries of varying types. Almost every one of those lists or libraries uses a view to display the content. SharePoint views define what and how you see content in a list or library. Is it sorted in descending order by the time the document was created, or is it grouped by a category field? Is some content filtered out by a priority field? Does one group of users need to see some fields in the list and others need to see fewer fields? All those things are what views do – they control how users see and can interact with the content.
I’ll just briefly mention a note on folders. Views are an organization tool, and they can replace subfolders in many cases, but not in all cases. I will discuss columns and metadata in another post, but just know that a view MAY be able to replace folders in some cases.
SharePoint views are classified first by the audience who uses the view:
The view audience is set when creating the view via a setting as a power user / administrator.
Beyond the audience, views can be of a few different starting types. Which one you choose will depend on how you want you to see and work with the data in that view from the start.
Some lists have certain views set to default. For example a Calendar list has the calendar view as default, but you can create a calendar view for any list that has date values on it. More often that not, typically there is an existing view that is mostly what you want that just needs to be tweaked. In that case, you can “start from an existing view” and modify as needed which really saves time.
The following minimum permissions are required by a user to create views:
Any user that has the contribute permission (can add, edit or delete content) can create a PERSONAL view. You have to have at least edit permission (SharePoint 2013) or design (SharePoint 2010) to create a PUBLIC view.
Attention Site Owners / Power Users
This next little section applies to folks with administrative privilege, so if that’s not you, you can skip to Use Cases. Who can create views can be customized via permission levels. While permissions are out of scope for this article, let me explain how they relate to views. Permission levels can be assigned like the following:
These basic permissions are made up of individual very granular permissions. For example, the Contribute permission level is made of these permissions:
It’s this specific Manage Personal Views permission that provides the ability for users to create personal views. This allows you to say a user can have Contribute, but not create personal views by creating a custom permission level. I will discuss this in a future basics blog. You can review a matrix of these permissions and levels here for SharePoint 2010 and here for SharePoint 2013.
Before we look at the how, I thought it would be good to give a few examples of how views can be useful. One of the worst things you can do is have a list or library with tons of content, and not spend 5 extra minutes and tweak the views to make it easy to work with!
Task Lists
Task lists by nature come with multiple views:
With any view, it’s powerful to use My type views to help dynamically target content to the logged in user. If so, you can set that view to be default so when Bob goes to the task list, he sees his tasks. If Jennifer goes to the list, she only sees her tasks (I show this down in the Dynamic Tokens in View Filters section below). Task lists also use field types like priority and category that can be grouped by or sorted, as well as date fields that yield a lot of possibilities. So if you want to see tasks past their due date, or tasks due within 2 days that are marked important... No problem!
Document Libraries
In document libraries, files have file sizes, so you could sort or filter to only show files that are at least 1 meg in size. Or if you have a lot of columns, you could make a summary (showed only basic fields) and full details views (that shows many views). Maybe you just want to see documents that the current user uploaded (My). If these are highly managed documents, views could be configured to show documents that need to be reviewed or are expiring within X days.
Issue Lists
Like task lists, issues lists have similar fields and are great candidates for defining some views. We use issues lists at C5 Insight to track client issues. Here’s one example that has 2 groupings, and some sorts:
All of these cases are extremely easy and would take minutes to configure. I cannot stress enough that I believe views are almost as important as the lists/libraries themselves. Does it take a user more than 3 major clicks to find the content they’re looking for? You likely need to tweak the view! Let’s take a look at how that is done.
You can see and switch views in a few different ways.
You can create a view via:
Starting a view from either way will load the exact same page.
You can customize / modify a view via:
Once this screen opens, the options are identical to when the view was created (with the exception that the web address for the view is now visible). Set your options as desired and click Ok.
In SharePoint 2013, accessing views is a little different.
Starting a view from either method will load the exact same page.
There are certain columns you might see when creating or editing a view, that might not be obvious as to what they are, or what they can be used for. I've tried to document them below. They are the same between both SharePoint platforms.
As I mentioned above, you can create views that are dynamic either to the user or a date. How is that done? There are two built-in values allowed that I call dynamic tokens:
I’m going to use an Accounts list I have created, loaded with multiple columns with different types of data like name, address, city, state, country, category, industry, number of employees, revenue, etc. By default it’s a big list of hundreds of records:
Recently Updated Accounts
Let’s create a view using [Today] to only show the most recently updated accounts. First, let’s sort by Modified descending then by Account Name ascending:
In the view filter settings, we can specify a formula using Modified:
What we’re saying is only show accounts that were modified within the last 2 days from today, and sort that list by the change date with newest at the top, then sort that by the Account Name in ascending order.
Wholesale Standard Accounts
We have a group of sales folks that only care about accounts whose industry = Wholesale, and whose Category = Standard. Easy, just create a view like before and set the following for the filter:
My Accounts
Let’s say we have a field in our account list called Salesperson that shows which sales person owns that account, and I have assigned a few accounts to me. Create your view, and set your filter:
Now we only see 4 accounts:
I hope this helps you to think of all the different ways you can put the power of views to work!
For more information about C5 Insight or this blog entry, please Contact Us.
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
Request Download
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.