SharePoint Column Validation Examples

Now available on Amazon!

Over 100 Examples!

A how-to book of formulas would not be too useful without a few examples. I've been collecting these for years. They've come from classroom questions, forum questions, and my own SharePoint sites. Now they are all in one place…

• Over 60 Calculated Columns examples
• Over 30 Column Validation examples
• 11 List/Library Item Validation examples
  (and every one of the Column Validation examples can be used here.)
• 7 Calculated Column Default Values examples
• 15 Workflow “workarounds” for things SharePoint formulas can’t do

Update 11/18/2017… added test for nearest 1/4th, 1/10th, etc.
Update 11/2/2015… added "Date must be the first day of the month" and "Date must be the last day of the month".

The following applies to SharePoint 2007, 2010, 2013, 2016 and SharePoint Online/Office 365.

 

Column Validation

SharePoint does not include column types for phone numbers or part numbers, nor does it include support for Regular Expressions to test for character patterns. It does support Excel style functions that we can use to create useful column validation formulas.

Below you will find column validation examples for:

• OR
• AND
• Length (LEN)
• Pattern matching using SEARCH and FIND
• Date testing

General Validation Formula Rules:

• Formula must return True or False.
• Column validations can only be added to Single Line of Text, Number, Choice (Drop-Down menu or Radio buttons, but not Checkboxes), Currency and Date and Time columns.
• Expressions are generally Excel compatible, but not all Excel functions can be used.
• Field names without special symbols can be entered as is or in square brackets
        = Price * [Qty]  > 100
• Field names with spaces or symbols must be enclosed in square brackets
        =OR( [Sales Region] = 1, [Sales Region] = 1)
• The text comparisons are not case sensitive.
        =OR( status = "a", status="c")     is true for either "A" or "a" or "C" or "c".
• In a column validation the formula cannot refer to another column.
• In a list / library validation the formula can refer to other columns in the same item.

Examples using "OR":

The OR function accepts two or more Boolean tests that each return True or False. OR returns True if any one of the tests is True.

=OR(YourFieldName="A",YourFieldName="C",YourFieldName="E")

=OR(State="OH", State="IN", State="KY", State="MI")

=OR(Qty=5, Qty=10, Qty=20)

Examples using "AND":

The AND function accepts two or more Boolean tests that each return True or False. AND returns True if all of the tests are True.

=AND(YourFieldName>"A", YourFieldName<"M")     YourFieldName value must be between A and M.

=AND(Qty>5, Qty<100, Qty<>47)      Qty must be between 5 and 100, but not 47.

Examples using "LEN":

As an example, if your part numbers are always 9 characters long:
    =LEN(YourFieldName) = 9

If the part numbers can be 9 or 12 characters long:
    =OR( LEN(YourFieldName) = 9, LEN(YourFieldName) = 12 )

Examples for Pattern Matching

The SEARCH function:  (online help)

• Matches a pattern using "*" and "?". "*" equals zero more characters and "?" equals exactly one character.
• To match an asterisks or question mark character prefix the symbols with "~". 
  Example: "a~?b?c" matches "a?bxc" but not "axbxc". 
• An "*" is assumed to be appended to the end of the match pattern. To limit the length use the AND and LEN functions.
• The comparison is not case sensitive.
• If there is a match, the function returns the position of the match. If the every character is to be matched you would typically test for "=1" or maybe ">0". 
• If there is no match, the function returns ERROR, therefore it must be wrapped inside of an ISERROR function. As we will have a match if there is no error, the ISERROR must be wrapped inside of a NOT function. (online help for ISERROR)

Examples:

Must start with an "a" or "A" and the third character must be a "c" or "C":
   =NOT(ISERROR( SEARCH("A?C",YourFieldName)=1 ))

   Matches: abc   AbC  aXc  a6c aBcDEF
   Does not match:   bbb   abb  ac  a

Match a phone number pattern of xxx-xxx-xxxx: (note: user could type letters or digits or type extra characters.)
   =NOT(ISERROR( SEARCH("???-???-????",YourFieldName)=1 ))

   Matches: 123-123-1234    aaa-aaa-aaaa   123-123-12344444

Match a phone number pattern of xxx-xxx-xxxx and limit the length:
   =AND( NOT(ISERROR(SEARCH("???-???-????",YourFieldName,1))), LEN(YourFieldName)=12 )

   Matches: 123-123-1234
   Does not match: 123-123-12345

Match a phone number and make sure only digits have been used:

The first example here is not a true pattern match. It just extracts the characters we think should be digits and tries to multiply them by any number. If that fails, then one or more of the characters is not a number. (online help for CONCATENATE and MID)

=NOT(ISERROR(1*CONCATENATE(MID(YourFieldName,1,3),MID(YourFieldName,5,3),MID(YourFieldName,9,4))))

   Matches: 123-123-1234    123x123x1234   123-123-1234xxxxx
   Does not match: abc-123-1234

The second example combines the earlier pattern match with a numeric test:

   =AND(NOT(ISERROR(SEARCH("???-???-????",YourFieldName,1))),LEN(YourFieldName)=12, NOT(ISERROR(1*CONCATENATE(MID(YourFieldName,1,3),MID(YourFieldName,5,3),MID(YourFieldName,9,4)))))

The FIND Function:  (online help)

The FIND function is similar to the SEARCH function with two differences;

• FIND is case sensitive.
• FIND does not support wild cards.

Examples for Numbers

Validate if a number ends in either .25, .50 or .5 or .75 or is a whole number.

     =ROUND([Activity Effort]*4,0)/4 = [Activity Effort]

If you wanted the number to the nearest 10th then divide by 10, round then multiple by 10.
     =ROUND([Activity Effort]*10,0)/10 = [Activity Effort]
This works all of the time for numbers with non-repeating digits. I.e. It will not work for 1/3 as 0.333333333333... can't be truly represented as a fixed set of digits. (It will actually work for 1/3 if you know the right number of digits to type! it looks like it's 15 significant digits: 0.333333333333333, 0.666666666666667 and 1.33333333333333 will work for 1/3, 2/3 and 1 1/3 with =ROUND([Activity Effort]*3,0)/3 = [Activity Effort] as the validation.)

Examples Using Dates

You can create rules to limit date ranges by using the TODAY() function or the DATEVALUE() function.

Date must be in the future:
    =YourFieldName>TODAY()

Date must be in the future by "x" days:
    =YourFieldName>TODAY() + 3
I.e. If today is the 7th, then valid dates start on the 11th.

Test against a particular date:  (online help for DATEVALUE)
    =YourFieldName>datevalue("1/1/2015")

Date must be between now and the end of the current year:  (online help for YEAR)
    =YourFieldName < DATEVALUE( "12/31/" & YEAR(TODAY()) )
This example calculates a DATEVALUE by building a string to represent a future date.

Date must be within the next 30 days:
    =AND(YourFieldName >= TODAY(),YourFieldName <= TODAY()+30)

Date must be a Monday:   (1 = Sunday, 2 = Monday, 3 = Tuesday, …)   (online help for WEEKDAY)
    =WEEKDAY(YourFieldName)=2

Date must be the last day of the month:
=DATE(YEAR(yourDateColumn),MONTH(yourDateColumn),DAY(yourDateColumn))=DATE(YEAR(yourDateColumn),MONTH(yourDateColumn)+1,0)

Date must be the first day of the month:
=DATE(YEAR(yourDateColumn),MONTH(yourDateColumn),DAY(yourDateColumn))=DATE(YEAR(yourDateColumn),MONTH(yourDateColumn),1)

Note: Some of the more "fun" Excel date functions like WEEKNUM, NETWORKDAYS and EOMONTH are not supported in SharePoint.

Not so useful tests!  

Value must be greater than PI.  (3.14159265358979 more or less…)
    =YourFieldName > PI()

And some square roots:
    =YourFieldName > SQRT(2)

And of course you need a little trig:
    =TAN(RADIANS(YourFieldName)) > 1

.

SharePoint Folders Are Not EVIL!

 

It seems that everyday I run across another blog article, forum post or social media that says “Never Use Folders!” While one of the common analogies for SharePoint is the Swiss Army Knife, a better one might be a tool box, and one with a lot of tools. Saying “Never Use Folders” is kind of like saying never use an adjustable wrench because we have box wrenches. Tools are tools and you need to select the correct tool for the job.

The following is not an excuse to not create a formal taxonomy and use a pure metadata approach to content management. It is a description of one of your many SharePoint tools in your toolbox. Remember everything is not a nail, and your only tool is not just a hammer.

 

Sometimes You Just Can’t Afford Metadata

Not an excuse so much as a reality.

You just built your new SharePoint farm. You have hundreds of thousands of documents to migrate to SharePoint. Who’s going to add all of the metadata? You employees (in their free time?), summer interns, contractors?

If you maintain the folder structure during your migration from network shares then your users can still find content as they always have. And, when you have added all of your metadata you can then either hide the old folders in your views, or move the content into one giant folderless library.

 

Folders are metadata!

In fact, Folders are “instant metadata”. Just upload or drag the document to the right folder and everyone will know something about it. If it’s in the folder named “Chlamydoselachidae” then it must be something about “Frill Sharks”!

(I’ll give anybody at Microsoft a couple of dollars if they will add the folder name property to the available columns in a view. It would then be true metadata!)

Folders can have custom metadata

A folder is a Content Type. You can create new Content Types that inherit from Folder and then add metadata columns. While a search on the metadata does not return the files in the folder, it will return the folders.

Here’s an article I wrote back in 2007 that still applies to SharePoint 2010, 2013 and 2016: http://techtrainingnotes.blogspot.com/2007/08/sharepoint-how-to-create-links-from.html

  

  

  

 

Want really smart folders with metadata that shares their metadata with their contents?

Take a look at Document Sets. Not the out of the box example, but rather a custom one that you create by inheriting from the Document Set Content Type. If you add a Site Column named “Product Category” then every document in that Folder / Document Set will be findable from search on that property. If you move a document from one Document Set to another Document Set, the document’s inherited metadata is updated to match!

https://technet.microsoft.com/en-us/library/ff603637.aspx

https://support.office.com/en-us/article/Introduction-to-Document-Sets-C49C246D-31F1-4BFE-AFE2-E26698B47E05

https://support.office.com/en-us/article/Create-and-configure-a-new-Document-Set-content-type-9DB6D6DC-C23A-4DCD-A359-3E4BBBC47FC1

 

Folders can be nested more than two levels deep

Using views and metadata you can create two levels of grouping. If you have SharePoint 2007 or 2010, you can use SharePoint Designer to create views that are up to 16 levels deep. But for SharePoint 2013 and 2016 they have changed (broken) SharePoint Designer so you can only group deeper than two levels by hand crafting XLST and HTML.

You can nest folders as much as needed, up to the maximum URL limits of Path to Library + Folders + Filename.

 

Folders are ideal for a rigid taxonomy

If the primary way of accessing content is by a single hierarchy then a folder structure may be the better choice. While still limited to the maximum length of a URL, it clearly supports more than the two levels offered by a grouped view.

  

Want a full crumb trail like we had in SharePoint 2007? See here: http://techtrainingnotes.blogspot.com/2015/11/add-crumb-trail-to-sharepoint-2013.html

 

Folders can be navigated using a Tree View

There are actually two tree views available, one out of the box, and one that is hidden.

The Quick Launch Tree View (Settings, Site Settings, Navigation Elements):

  

The hidden SharePoint 2010 “Navigate Up” button:

(See: http://techtrainingnotes.blogspot.com/2014/06/sharepoint-2013-restoring-2010-navigate.html)

  

Note: Currently neither Tree View is available in the “new library experience” for SharePoint Online, and one day for SharePoint 2016 on premises.

 

Metadata is not always searchable as a property

Unless you have created Site Columns, and configured them as friendly search Managed Properties, then as far as seach is concerned, all of those columns of metadata might have just been typed into a single “Keywords” column.

 

Search Likes Folders

Search includes several managed properties to make finding folders and content in folders easy to do. Unlike Site Columns, these folder properties do not require any Search Service setup to work.

Path:    path:https://yourServer/sites/site/library/folder
            path:"https://yourserver/sites/taxonomy/Fish/Agnatha and Lampreys/Myxini/Myxiniformes"

Searching with Path works, and is very precise, and returns all of the content in that path. The negative is typing the full path to the folder.

contenttype:folder     contenttype:folder Myxiniformes

contenttype finds all folders and all content types that inherit from Folder. (This will also return folders that have a column with the keywords being searched. In the example above you will get folders with “Myxiniformes” in the folder name and folders with a column with “Myxiniformes” in its name.)

IsContainer:true        IsContainer:true Myxiniformes

IsContainer returns Sites, Libraries and Folders that have the keyword in their name or metadata. IsContainer also returns Team Site Notebooks (OneNote files) and content stored in Asset libraries (The thing you click on in an Asset library is a folder, not the actual picture or video.) as they are represented as folders.

Library search box

The search box at the top of each library assumes you only want to search the content in the current folder! (You can then click “Some files might be hidden. Include these in your search” to search the rest of the library.)

  

 

Microsoft / SharePoint Really Likes Folders!

Take a look at OneDrive for Business… you can’t even add metadata columns or use Content Types. “Name”, “Modified”, “Modified by”, “File Size” and “Sharing” are all you get. The only “metadata” I can add is by using folders.

   
    (Yes, I really have a folder named “junk”!)

In my OneDrive I have to embed metadata in the filename and/or the folder structure. Kind of like network shares!

   

 

The New Library Experience likes folders!

The new library experience in Office 365 makes it easy to arrange and rearrange documents by folder. (Seems to encourage the use of folders!)

   

 

Sync Only Sync’s Folders

All three of the sync clients only sync folder structure, not metadata. If you want any obvious classification of your local sync of the content then you have to use folders. The only metadata you can add from client side is in the filename and the location/folder.

 

Security and Folders

Remember when Microsoft’ advise was to never use item level permissions? At least until SharePoint 2013 where they gave everybody a “Share” button. Now SharePoint 2013 and 2016 encourage users to break inheritance everywhere!

See here for what can happen with unlimited use of the Share buttons: http://techtrainingnotes.blogspot.com/2015/10/trick-or-treat-day-in-life-of.html

For a simple example consider:

1. We create a site for Sales Managers. We create a library for their files.
2. The sales managers start clicking the Share links on various documents, most to share with the “Summer Interns” group and the “Marketing Team” group. Over time there are 500 items with broken inheritance.
3. Management asks you to add Regional Sales Managers to the site, with their own group.
4. You create a SharePoint group and add the Sales Managers and grant it access to the site.
5. The Regional Managers visit the site and complain that they can’t find all of the files the Sales Managers have told them about.
6. You now have to:
   1. Find the 500 files with broken inheritance.
   2. Grant permissions to each of the files to the Regional Managers group.

So what can you do? Use folders for permissions.

1. Create the library.
2. Add a folder for “Everyone”. (Optional as the files in the root of the library will be available to everyone by default.)
3. Add a folder for “Sales Managers Only”. Break inheritance and grant permissions to the Sales Managers group.
4. Add a folder for “Visible to Marketing Team”. Break inheritance and grant permissions to the Sales Managers group and to the Marketing Team group.
5. Add a folder for “Visible to Interns”. Break inheritance and grant permissions to the Sales Managers group and to the Interns group.
6. Create a new view named “Sales Files”:
   1. Make it the default view.
   2. In the Folders section hide the folders.

Users will now see a single list of content, which can also be grouped using metadata, but they will only be able to see the content they should see. The users who maintain the content use the AllItems view so they can quickly upload documents into the correct folder, and automatically apply the correct permissions. (Now all you have to do is hide those pesky Share buttons! http://techtrainingnotes.blogspot.com/2015/08/hiding-evil-sharepoint-2013-share.html)

 

So which should you use?
  Folders or
    Metadata+Views or
      Folders+Metadata+Views?

Use the best tool for the job!

 

.

SharePoint PowerShell Training for Auditing and Site Content Administration

 

If you have followed this blog, you know that I’m kind of a SharePoint nut who’s also a PowerShell nut. Over the years I have created a lot of PowerShell scripts while working with SharePoint and answering questions in my classes and in the TechNet forums. There’s plenty of resources for installing and configuring SharePoint using PowerShell, but there’s little on dealing with all of the daily questions on premise admins get that can be quickly answered using PowerShell. I was just going to take my 100+ scripts and create something like a “cookbook”, but instead created a class. The class handout kind of ended up as the cookbook… 85 pages and 175 sample scripts, or maybe more like a giant PowerShell cheatsheet for SharePoint.

This class is for on-premise SharePoint 2010, 2013 and 2016 administrators. A SharePoint Online version is in the works, but not available yet.

If you would like to attend this class, delivered by the author (your’s turely!), we are offering it next Monday, March 14th, at MAX Technical Training in Cincinnati, Ohio. You can attend this class at MAX or remotely from anywhere. If you can’t attend this class, it is available from trainging centers all over the world.

March 14th class at MAX: SharePoint 2010 and 2013 Auditing and Site Content Administration using PowerShell

Search for this class at other training centers: https://www.bing.com/search?q=55095%20powershell

If you would like to see some of the other courses and books I’ve written, then click here.

 

55095 SharePoint 2010 and 2013 Auditing and Site Content Administration using PowerShell

This one day instructor-led class is designed for SharePoint 2010 and 2013 server administrators and auditors who need to query just about anything in SharePoint. The class handout is effectively a cheat sheet with over 175 PowerShell scripts plus the general patterns to create your own scripts. These scripts cover:

• using the SharePoint Management Shell and the ISE
• general tips for counting, reformatting and exporting results;
• drilling up and down the SharePoint object model
• getting lists / inventories of servers, services web applications, sites, webs, lists, libraries, items, fields, content types, users and much more
• finding lists by template type, content type and types of content
• finding files by user, content type, file extension, checked out status, size and age
• finding inactive sites
• finding and changing SharePoint Designer settings and finding and resetting customized pages
• inventorying and managing features
• deleting and recycling files and list items
• inventorying users and user permissions and finding out “who can access what”
• creating sites, lists and libraries
• uploading and downloading files
• and much more…

At Course Completion

After completing this course, students will be able to:

• Use PowerShell to query just about anything inside of SharePoint.
• Understand the core SharePoint object model and object hierarchy as seen from PowerShell.
• Format PowerShell output in to reports.
• Manage resources to limit the impact on production servers.
• Create and delete Site Collections, subsites, lists, libraries and content.

Prerequisites

Before attending this course, students must:

• Very good knowledge of SharePoint and its features.
• Good experience using PowerShell 2 or later or recent completion of a PowerShell class such as 10961 or 50414.

Course Outline

Module 1:  SharePoint and PowerShell

This module provides an introduction to the topics covered in the class, introduces SharePoint PowerShell terminology and provides a review of important PowerShell features.

Lessons:

• History of PowerShell in SharePoint
• PowerShell vs. Search
• PowerShell, SharePoint Management Shell and cmdlets
• Security and Permissions Needed
• Getting Started with PowerShell: Counting Items, Custom Columns, Reformatting Numbers, Saving Results to a File
• Changing and Updating Content: Creating SharePoint Objects, Changing Objects

Lab:

• Using PowerShell with SharePoint

After completing this module, students will be able to:

• Get started using PowerShell to inventory and update SharePoint.

Module 2: Working with SharePoint CMDLETs and Objects

This module introduces the SharePoint object model and some important terminology.

Lessons:

• GUIDs
• Sites vs. Webs
• The SharePoint Object Hierarchy

Lab:

• Get a list of all Site Collections and their GUIDs
• Get a list of all Webs in all Site Collections
• Given a web’s URL get its parent web and web application

After completing this module, students will be able to:

• Explore sites and webs using PowerShell.
• Retrieve important properties of common SharePoint objects

Module 3: Managing Memory and Limiting Performance Impact

This explores limiting impact on server memory usage and performance.

Lessons:

• Memory Management and Disposing Objects
• Limiting Impact on Production Servers

Lab:

• Exploring PowerShell’s use of system memory.
• Testing the impact of scripts on server performance

After completing this module, students will be able to:

• Recognize and manage the impact of PowerShell on a SharePoint server.

Module 4: Working with Content

This module explores SharePoint using PowerShell from the Farm down to individual list items.

Lessons:

• Getting Farm Information: version, services, services, features
• Getting Web Application information
• Exploring Site Collections: retrieve Site Collections, Site Collection Administrators, quotas
• Working with the Recycle Bins: finding items, getting file counts and bytes, deleted sites
• Exploring Webs: web templates, finding webs, finding webs based on template, Quick Launch and Top Link Bar navigation
• Exploring Lists and Libraries: finding all lists, lists by type, lists by Content Type, columns/fields, document count by web or library
• Exploring Content Types
• Finding documents: by a word in the title, file type, content type, size, date age, checked out status, approval status and many more…
• Deleting content
• Downloading and uploading files

Lab:

• Explore the farm.
• Inventory site collections.
• Create a recycle bin report.
• Finding all blog sites.
• Find all picture libraries.
• Find all PDF files over 5 MB.
• Delete all videos in a site collection.

After completing this module, students will be able to:

• Explorer, inventory and maintain SharePoint content using PowerShell.

Module 5: Users and Security

This module covers the use of PowerShell to explore and document SharePoint permissions.

Lessons:

• Users: find a user, get a list of all users, working with Active Directory groups
• SharePoint groups: Get lists of groups, get the members of a group, find all groups a user belongs to, find the groups associated with a web
• Expanding users lists that include Active Directory groups
• Documenting Broken Inheritance / Unique Permissions: webs, lists, libraries, folders, items
• Working with Role Assignments

Lab:

• Get a list of all users who have access to a Site Collection.
• Get a list of all groups in a Site Collection.
• Get a list of all groups a user belongs to.
• List all users who may have access to a SharePoint securable.
• Get a list of all securables with broken inheritance.

After completing this module, students will be able to:

• Explore and document users and user permissions.
• Explore and document SharePoint groups.
• Explore and document broken inheritance.

Module 6: Managing Sites

This module explorers Site Collection and Web management from PowerShell.

Lessons:

• Finding Inactive Webs
• Creating and Deleting Site Collections
• Getting Site Collection Data
• Creating and Deleting Subsites
• Working With SharePoint Designer Settings

Lab:

• Create a report for inactive sites.
• Create a site collection and subsites.
• Delete a site.
• Delete a site collection.
• Disable SharePoint Designer in all site collections.

After completing this module, students will be able to:

• Manage SharePoint Site Collections and webs from PowerShell.

Audience

• SharePoint server administrators.
• SharePoint auditors.
• Also valuable for SharePoint developers.

Hide the Attachments Link in a SharePoint Form

 

The problem… While we do want site visitors to see the list items, we don’t want them to see or click the list’s attachments.

More SharePoint Customization tricks!
More Site Owner articles.
More articles about the SPSecurityTrimmedControl

One approach is to use CSS and a handy SharePoint control. You could also write a JavaScript solution. Here we will look at the CSS option.

Note: This is not security! This is hiding some HTML using CSS. Users can right-click and select View Source to discover the text hidden by the CSS.

 

General pattern:

1. View the DispForm.aspx page (the view properties popup in SP 2010) for an item in the list.
2. Press F12 to open the IE Developer Tools.
3. Use the Internet Explorer F12 panel’s Select Element button to discover an appropriate tag and ID that could changed by CSS to show/hide the content.  (For this example it happens to be “idAttachmentsRow”.)
   
4. Edit the DispForm.aspx page using SharePoint Designer.
5. Add CSS to hide the tag from everyone.
6. Add a SharePoint control with additional CSS to unhide the content for users with at least the Edit permission. Set the SharePoint control to only display its content for people who can edit list items.

The SPSecurityTrimmedControl

The magic here is that the SPSecurityTrimmedControl can selectively display content based on a user’s assigned permission. As an example, users with the Read permission level do not have the EditListItems permission while members and owners do. Note that the control can only be set to a single permission, not a Permission Level or group.

More detailed steps:

1. Open SharePoint Designer and your site.
2. Click Lists and Libraries and your list.
3. Click the DispForm.aspx file.
4. In the ribbon click Advanced Mode.
5. Find the PlaceholderMain Content tag (<asp:Content ContentPlaceHolderId="PlaceHolderMain" runat="server">)
6. Add the following block of HTML just after that tag.
7. Save your changes and test.

 

SharePoint 2010 (and probably 2007) version:

<style type="text/css">
  #idAttachmentsRow { display:none }
</style>
<Sharepoint:SPSecurityTrimmedControl runat="server" PermissionsString="EditListItems">
  <style type="text/css">
    #idAttachmentsRow { display:inline }
  </style>
</Sharepoint:SPSecurityTrimmedControl>

SharePoint 2013 and SharePoint Online / O365 (and probably 2016) version:

<style type="text/css">
  #idAttachmentsRow { display:none !important }
</style>
<Sharepoint:SPSecurityTrimmedControl runat="server" PermissionsString="EditListItems">
  <style type="text/css">
    #idAttachmentsRow { display:table-row !important}
  </style> 
</Sharepoint:SPSecurityTrimmedControl>

A list of the PermissionsStrings can be found here: https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spbasepermissions.aspx

More about using SPSecurityTrimmedControl can be found here: http://techtrainingnotes.blogspot.com/2009/07/sharepoint-run-javascript-based-on-user.html

 

.

“Unable to display this Web Part” after XSLT Customization

The following applies to SharePoint 2013, 2016 and SharePoint Online.

 

The Error

“Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Microsoft SharePoint Foundation-compatible HTML editor such as Microsoft SharePoint Designer. If the problem persists, contact your Web server administrator.”

The above error shows up in SharePoint 2013 and later when doing multi-level grouping with Data Form Web Parts. With the removal of many of the design features from SharePoint Designer 2013, I doubt there are too many people creating new XSLT customization. But if you are upgrading from 2010 or trying to implement a 2010 style customization then you many run into this error.

 

The Cause and the Fix

If you dig into the error logs you will find that this is reported as “Error while executing web part: System.StackOverflowException”. Turns out though that it is a timeout of the XSLT parser and has been around for quite a while. The fix is pretty easy, if you are on premises, just run a tiny PowerShell script from the SharePoint Management Shell.

$farm = Get-SPFarm
$farm.XsltTransformTimeOut = 10
$farm.Update()

Some of the articles say to increase it from the default of 1 second to 5 seconds. In my test environment I typically needed to increase it to 10 seconds. If you monitor the CPU on the server you will see that at least on lab-type virtual machines that a page load where you have this issue does put quite a load on the CPU.

SharePoint Online?  No joy for you! It appears that the default is 1 second, and you can’t change it.

 

There’s been a number of articles on the topic, mostly in the SP 2010 world:

http://thechriskent.com/tag/xslttransformtimeout/

http://blogs.msdn.com/b/joerg_sinemus/archive/2012/03/07/xslt-and-timeout-problem-when-transforming-runs-more-than-one-second.aspx

and many more: http://www.bing.com/search?q=xslttransformtimeout+sharepoint

 

.

Views.Add() Cannot find an overload for "Add" and the argument count: "8".

 

I wrote a PowerShell script to create views. It worked in PowerShell 3 on SharePoint 2013. It failed in PowerShell 2 on SharePoint 2010.

To play it safe, I copied values from an existing view to insure the correct data types…

$web = Get-SPWeb http://sharepoint/sites/training
$list = $web.lists["Announcements22"]
$v = $list.views[0]
$list.Views.add("TestView",$v.ViewFields,$v.query,30,$true,$false,$v.Type,$false)

As I can count to 8 (usually) and I made sure the data types were correct, I then wasted a lot of time google/binging the error message.

So I then did the obvious thing for a developer, I fired up Visual Studio. And… found that there’s a datatype weirdness on the ViewFields parameter! The Add method is expecting System.Collections.Specialized.StringCollection while the View object actually returns Microsoft.SharePoint.SPViewFieldCollection.

The type conversion works in PowerShell 3:

But does not work in PowerShell 2:

 

My workaround? 

Use a handy method built into the Microsoft.SharePoint.SPViewFieldCollection type: ToStringCollection().

I could also have created the StringCollection object and copied the strings over using ForEach.

 

So why did it work in PowerShell 3 and not PowerShell 2? No idea! I’m guessing the “smarts” behind type conversion has improved. While the two collection objects are different (SPViewFieldCollection includes a .View property), the Items collection of both contain simple Strings.

 

.

SharePoint: Generate a report of inactive sites and owners

This article is for SharePoint 2007, 2010, 2013 and 2016 on premises. (2007 users see the note at the end of the article.)

Cleaning up inactive sites is a common best practice administrator activity. Finding these sites and getting a list of who to contact can take a bit of work. Here's a little PowerShell script to generate a report of all inactive sites, their Site Collection Administrators and their Full Control users.

 

Inactive Site?

Each web has a property named LastItemModifiedDate that can be used as one criteria for site activity. I say "one criteria" as the site may not have had been updated in months, but users still visit the site and view the content every day. In the scripts below we check for the inactivity using a Where that tests against a calculated date:

Where { $_.LastItemModifiedDate -lt ((Get-Date).AddMonths(-9)) }

You can change the test date by using AddDays, AddMonths and AddYears with negative numbers to "go back in time". The example above looks for webs not updated in the last 9 months.

Note: The LastItemModifiedDate (and all other internal SharePoint dates) is in GMT. To convert to local time use ".ToLocalTime()".

 

Create a report…

The following script generates a report that lists each web, last updated date, Site Collection Administrators and Full Control users. Note that if you added an Active Directory group with Full Control, only the group name will be listed, not all of the member users.

Get-SPSite -Limit All | 
  Get-SPWeb -Limit All | 
  Where { $_.LastItemModifiedDate -lt ((Get-Date).AddMonths(-9)) } |
  foreach {
    # the URL
    ""   #blank line
    $_.url
    "  LastItemModifiedDate: " + $_.LastItemModifiedDate
    "  Web has unique permissions: " + $_.HasUniquePerm

    # the Site Collection Administrators
    " Site Collection Administrators:"
    foreach ($user in $_.SiteAdministrators)
    {      
       "  " + $user.DisplayName + " " + $user.UserLogin
    }

    # full control users
    " Full Control Users:"
    foreach ($user in $_.Users)
    {
       if ( $_.DoesUserHavePermissions($user,[Microsoft.SharePoint.SPBasePermissions]::FullMask) )      
       { 
         "  " + $user.DisplayName + " " + $user.UserLogin
       }
    }
  }

 

Create a customized SPWeb object for further pipelining…

If you would rather have an output that can be piped on to other cmdlets then use the following script. It adds a PowerShell NoteProperty to each SPWeb object named FullControlUsers can be accessed as if it was a built-in property.

Get-SPSite -Limit All | 
  Get-SPWeb -Limit All | 
  Where { $_.LastItemModifiedDate -lt ((Get-Date).AddMonths(-9)) } |
  foreach {
  
    $TTNusers = @();   #empty collection

    foreach ($user in $_.Users)
    {
       if ( $_.DoesUserHavePermissions($user,[Microsoft.SharePoint.SPBasePermissions]::FullMask) )      
       { 
         $TTNusers += $user;  # add to the collection
       }
    }

    # add the new property
    $_ | Add-Member -type NoteProperty -name FullControlUsers -value $TTNusers;

    # forward the modified SPWeb object on through the piepline.
    $_;

  } | 
  Select Url, SiteAdministrators, FullControlUsers 

Or maybe change the "Select" to "Format-List":

 

Performance Tip

If this script is run during business hours on a large farm you could impact your users. Consider adding a Start-Sleep cmdlet just after the foreach to insert a small delay between webs. But of course, that will make your script take longer to complete.

.

For SharePoint 2007

Replace:

Get-SPSite -Limit All | Get-SPWeb -Limit All |

With:

[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.Administration")
$webapp = [Microsoft.SharePoint.Administration.SPWebApplication]::Lookup("http://maxsp2013wfe")
$webapp.sites | Select -ExpandProperty AllWebs |

 

..

SharePoint Content Type Inheritance

This article applies to SharePoint 2010, 2013 and 2016.

If you have worked around SharePoint for a while then you have heard the phrase "Everything is a list…". If everything is a list then everything should be an "item", right? Turns out that that is almost a fact. With the exception of only a handful of Content Types, they all inherit from"Item". In the end everything inherits from a base type named "System". The listing below is from a 2013 publishing site with a few extra features enabled to find as many Content Types as possible. The 2016 list is very similar, but is missing some of the Business Intelligence content types (Excel Services?).

A few examples:

• Task <- Item <- System
• Document <- Item <- System
• Video <- System Media Collection <- Document Set <- Document Collection Folder <- Folder <- Item <- System

What does not inherit from Item?

• Common Indicator Columns <- System  (hidden)
• And the types that inherit from it:
  • Excel based Status Indicator <- Common Indicator Columns <- System
  • Fixed Value based Status Indicator <- Common Indicator Columns <- System
  • SharePoint List based Status Indicator <- Common Indicator Columns <- System
  • SQL Server Analysis Services based Status Indicator <- Common Indicator Columns <- System

 

PowerShell to the rescue… again.

To dump the hierarchy of Content Types I wrote a little PowerShell script that uses a recursive function. Just edit the URL to your site and you can get your list of Content Types.

If you wanted to see the inheritance pattern another way, add the ID of the Content Type to your output, or just do a test like the following and note the pattern in the IDs:

  $web.ContentTypes | sort id | Select id, name

 

The PowerShell script:

function Get-CTypeParent ($ctype, $TTNstr)
{
  if ($ctype.name -NE "System") {
   $TTNstr = $TTNstr + " <- " + $ctype.parent.name;
   $TTNstr = Get-CTypeParent $ctype.parent $TTNstr 
   }
  return $TTNstr;
}

$site = Get-SPSite http://yourserver/sites/yourSite
$web = $site.RootWeb

$web.ContentTypes | sort Group, Name | 
  group Group | 
    foreach { $_.Group  | 
                     foreach 
                       -Begin {"`n" + $_.Name} 
                       -Process { $str="  " + $_.Name ;  Get-CTypeParent $_ $str } 
            }

 

The list of Content Types and their family history!

This list is from SharePoint 2013. The 2016 list is very similar, but is missing some of the Business Intelligence content types (Excel Services?).

_Hidden

  Administrative Task <- Task <- Item <- System

  Approval Workflow Task (en-US) <- SharePoint Server Workflow Task <- Workflow Task <- Task <- Item <- System

  Collect Feedback Workflow Task (en-US) <- SharePoint Server Workflow Task <- Workflow Task <- Task <- Item <- System

  Collect Signatures Workflow Task (en-US) <- SharePoint Server Workflow Task <- Workflow Task <- Task <- Item <- System

  Common Indicator Columns <- System

  Design File <- Document <- Item <- System

  Device Channel <- Item <- System

  Device Channel Mappings <- Document <- Item <- System

  Display Template <- Document <- Item <- System

  Display Template Code <- Display Template <- Document <- Item <- System

  Document Collection Folder <- Folder <- Item <- System

  DomainGroup <- Item <- System

  Health Analyzer Report <- Item <- System

  Health Analyzer Rule Definition <- Item <- System

  InfoPath Form Template <- Document <- Item <- System

  Office Data Connection File <- Document <- Item <- System

  Page Output Cache <- Item <- System

  PerformancePoint Base <- Item <- System

  PerformancePoint Monitoring Document Type <- Document <- Item <- System

  Person <- Item <- System

  Project Policy <- Item <- System

  Published Link <- Item <- System

  Publishing Approval Workflow Task (en-US) <- SharePoint Server Workflow Task <- Workflow Task <- Task <- Item <- System

  Reusable HTML <- Item <- System

  Reusable Text <- Item <- System

  RootOfList <- Folder <- Item <- System

  Rule <- Item <- System

  SharePoint Server Workflow Task <- Workflow Task <- Task <- Item <- System

  SharePointGroup <- Item <- System

  Signatures Workflow Task Deprecated <- SharePoint Server Workflow Task <- Workflow Task <- Task <- Item <- System

  System

  System Master Page <- Document <- Item <- System

  System Media Collection <- Document Set <- Document Collection Folder <- Folder <- Item <- System

  System Page <- Document <- Item <- System

  System Page Layout <- Document <- Item <- System

  Translation Package <- Document <- Item <- System

  Translation Status <- Document <- Item <- System

  Universal Data Connection File <- Document <- Item <- System

  User Workflow Document <- Document <- Item <- System

  Workflow History <- Item <- System

  Workflow Task <- Task <- Item <- System

  WorkflowServiceDefinition <- Item <- System

  WorkflowServiceSubscription <- Item <- Systemvi

Business Intelligence

  Excel based Status Indicator <- Common Indicator Columns <- System

  Fixed Value based Status Indicator <- Common Indicator Columns <- System

  Report <- Document <- Item <- System

  Report Document <- Document <- Item <- System

  SharePoint List based Status Indicator <- Common Indicator Columns <- System

  SQL Server Analysis Services based Status Indicator <- Common Indicator Columns <- System

  Web Part Page with Status List <- Document <- Item <- System

Community Content Types

  Category <- Item <- System

  Community Member <- Site Membership <- Item <- System

  Site Membership <- Item <- System

Digital Asset Content Types

  Audio <- Rich Media Asset <- Document <- Item <- System

  Image <- Rich Media Asset <- Document <- Item <- System

  Rich Media Asset <- Document <- Item <- System

  Video <- System Media Collection <- Document Set <- Document Collection Folder <- Folder <- Item <- System

  Video Rendition <- Rich Media Asset <- Document <- Item <- System

Display Template Content Types

  Control Display Template <- Display Template <- Document <- Item <- System

  Filter Display Template <- Display Template <- Document <- Item <- System

  Group Display Template <- Display Template <- Document <- Item <- System

  Item Display Template <- Display Template <- Document <- Item <- System

  JavaScript Display Template <- Document <- Item <- System

Document Content Types

  Basic Page <- Document <- Item <- System

  Document <- Item <- System

  Dublin Core Columns <- Document <- Item <- System

  Form <- Document <- Item <- System

  Link to a Document <- Document <- Item <- System

  List View Style <- Document <- Item <- System

  Master Page <- Document <- Item <- System

  Master Page Preview <- Document <- Item <- System

  Picture <- Document <- Item <- System

  Web Part Page <- Basic Page <- Document <- Item <- System

  Wiki Page <- Document <- Item <- System

Document Set Content Types

  Document Set <- Document Collection Folder <- Folder <- Item <- System

Folder Content Types

  Discussion <- Folder <- Item <- System

  Folder <- Item <- System

  Summary Task <- Folder <- Item <- System

Group Work Content Types

  Circulation <- Item <- System

  Holiday <- Item <- System

  New Word <- Item <- System

  Official Notice <- Item <- System

  Phone Call Memo <- Item <- System

  Resource <- Item <- System

  Resource Group <- Item <- System

  Timecard <- Item <- System

  Users <- Item <- System

  What's New Notification <- Item <- System

List Content Types

  Announcement <- Item <- System

  Comment <- Item <- System

  Contact <- Item <- System

  East Asia Contact <- Item <- System

  Event <- Item <- System

  Issue <- Item <- System

  Item <- System

  Link <- Item <- System

  Message <- Item <- System

  Post <- Item <- System

  Reservations <- Event <- Item <- System

  Schedule <- Event <- Item <- System

  Schedule and Reservations <- Event <- Item <- System

  Task <- Item <- System

  Workflow Task (SharePoint 2013) <- Task <- Item <- System

Page Layout Content Types

  Article Page <- Page <- System Page <- Document <- Item <- System

  Catalog-Item Reuse <- Page <- System Page <- Document <- Item <- System

  Enterprise Wiki Page <- Page <- System Page <- Document <- Item <- System

  Error Page <- Page <- System Page <- Document <- Item <- System

  Project Page <- Enterprise Wiki Page <- Page <- System Page <- Document <- Item <- System

  Redirect Page <- Page <- System Page <- Document <- Item <- System

  Welcome Page <- Page <- System Page <- Document <- Item <- System

PerformancePoint

  PerformancePoint Dashboard <- PerformancePoint Base <- Item <- System

  PerformancePoint Data Source <- PerformancePoint Monitoring Document Type <- Document <- Item <- System

  PerformancePoint Filter <- PerformancePoint Base <- Item <- System

  PerformancePoint Indicator <- PerformancePoint Base <- Item <- System

  PerformancePoint KPI <- PerformancePoint Base <- Item <- System

  PerformancePoint Report <- PerformancePoint Base <- Item <- System

  PerformancePoint Scorecard <- PerformancePoint Base <- Item <- System

Publishing Content Types

  ASP NET Master Page <- System Master Page <- Document <- Item <- System

  Html Master Page <- ASP NET Master Page <- System Master Page <- Document <- Item <- System

  Html Page Layout <- Page Layout <- System Page Layout <- Document <- Item <- System

  Page <- System Page <- Document <- Item <- System

  Page Layout <- System Page Layout <- Document <- Item <- System

Special Content Types

  Unknown Document Type <- Document <- Item <- System

 

The List Sorted By Ancestor

Change the last line of the script to the following and you can see another pattern in the inheritance.

$web.contenttypes | sort group, name | group group | foreach { $_.Group  | foreach -begin {"`n" + $_.Name} -process { $str="  " + $_.name ;  Get-CTypeParent $_ $str } }

System ->   Item

System -> Item ->   Announcement

System -> Item ->   Circulation

System -> Item ->   Comment

System -> Item ->   Contact

System -> Item ->   Device Channel

System -> Item ->   Document

System -> Item ->   DomainGroup

System -> Item ->   East Asia Contact

System -> Item ->   Event

System -> Item ->   Folder

System -> Item ->   Health Analyzer Report

System -> Item ->   Health Analyzer Rule Definition

System -> Item ->   Holiday

System -> Item ->   Issue

System -> Item ->   Link

System -> Item ->   Message

System -> Item ->   New Word

System -> Item ->   Official Notice

System -> Item ->   Page Output Cache

System -> Item ->   PerformancePoint Base

System -> Item ->   Person

System -> Item ->   Phone Call Memo

System -> Item ->   Post

System -> Item ->   Published Link

System -> Item ->   Resource

System -> Item ->   Resource Group

System -> Item ->   Reusable HTML

System -> Item ->   Reusable Text

System -> Item ->   Rule

System -> Item ->   SharePointGroup

System -> Item ->   Task

System -> Item ->   Timecard

System -> Item ->   Users

System -> Item ->   What's New Notification

System -> Item ->   Workflow History

System -> Item ->   WorkflowServiceDefinition

System -> Item ->   WorkflowServiceSubscription

System -> Item -> Document ->   Basic Page

System -> Item -> Document ->   Design File

System -> Item -> Document ->   Device Channel Mappings

System -> Item -> Document ->   Display Template

System -> Item -> Document ->   Dublin Core Columns

System -> Item -> Document ->   Form

System -> Item -> Document ->   InfoPath Form Template

System -> Item -> Document ->   JavaScript Display Template

System -> Item -> Document ->   Link to a Document

System -> Item -> Document ->   List View Style

System -> Item -> Document ->   Master Page

System -> Item -> Document ->   Master Page Preview

System -> Item -> Document ->   Office Data Connection File

System -> Item -> Document ->   PerformancePoint Monitoring Document Type

System -> Item -> Document ->   Picture

System -> Item -> Document ->   Report Document

System -> Item -> Document ->   Rich Media Asset

System -> Item -> Document ->   System Master Page

System -> Item -> Document ->   System Page

System -> Item -> Document ->   System Page Layout

System -> Item -> Document ->   Translation Package

System -> Item -> Document ->   Translation Status

System -> Item -> Document ->   Universal Data Connection File

System -> Item -> Document ->   Unknown Document Type

System -> Item -> Document ->   User Workflow Document

System -> Item -> Document ->   Wiki Page

System -> Item -> Document -> Basic Page ->   Web Part Page

System -> Item -> Document -> Display Template ->   Control Display Template

System -> Item -> Document -> Display Template ->   Display Template Code

System -> Item -> Document -> Display Template ->   Filter Display Template

System -> Item -> Document -> Display Template ->   Group Display Template

System -> Item -> Document -> Display Template ->   Item Display Template

System -> Item -> Document -> PerformancePoint Monitoring Document Type ->   PerformancePoint Data Source

System -> Item -> Document -> Rich Media Asset ->   Audio

System -> Item -> Document -> Rich Media Asset ->   Image

System -> Item -> Document -> Rich Media Asset ->   Video Rendition

System -> Item -> Document -> System Master Page ->   ASP NET Master Page

System -> Item -> Document -> System Master Page -> ASP NET Master Page ->   Html Master Page

System -> Item -> Document -> System Page ->   Page

System -> Item -> Document -> System Page -> Page ->   Article Page

System -> Item -> Document -> System Page -> Page ->   Catalog-Item Reuse

System -> Item -> Document -> System Page -> Page ->   Enterprise Wiki Page

System -> Item -> Document -> System Page -> Page ->   Error Page

System -> Item -> Document -> System Page -> Page ->   Redirect Page

System -> Item -> Document -> System Page -> Page ->   Welcome Page

System -> Item -> Document -> System Page -> Page -> Enterprise Wiki Page ->   Project Page

System -> Item -> Document -> System Page Layout ->   Page Layout

System -> Item -> Document -> System Page Layout -> Page Layout ->   Html Page Layout

System -> Item -> Event ->   Reservations

System -> Item -> Event ->   Schedule

System -> Item -> Event ->   Schedule and Reservations

System -> Item -> Folder ->   Discussion

System -> Item -> Folder ->   Document Collection Folder

System -> Item -> Folder ->   RootOfList

System -> Item -> Folder ->   Summary Task

System -> Item -> Folder -> Document Collection Folder ->   Document Set

System -> Item -> Folder -> Document Collection Folder -> Document Set ->   System Media Collection

System -> Item -> Folder -> Document Collection Folder -> Document Set -> System Media Collection ->   Video

System -> Item -> PerformancePoint Base ->   PerformancePoint Dashboard

System -> Item -> PerformancePoint Base ->   PerformancePoint Filter

System -> Item -> PerformancePoint Base ->   PerformancePoint Indicator

System -> Item -> PerformancePoint Base ->   PerformancePoint KPI

System -> Item -> PerformancePoint Base ->   PerformancePoint Report

System -> Item -> PerformancePoint Base ->   PerformancePoint Scorecard

System -> Item -> Task ->   Administrative Task

System -> Item -> Task ->   Workflow Task

System -> Item -> Task ->   Workflow Task (SharePoint 2013)

System -> Item -> Task -> Workflow Task ->   PSWApprovalTask

System -> Item -> Task -> Workflow Task ->   SharePoint Server Workflow Task

System -> Item -> Task -> Workflow Task -> SharePoint Server Workflow Task ->   Approval Workflow Task (en-US)

System -> Item -> Task -> Workflow Task -> SharePoint Server Workflow Task ->   Collect Feedback Workflow Task (en-US)

System -> Item -> Task -> Workflow Task -> SharePoint Server Workflow Task ->   Collect Signatures Workflow Task (en-US)

System -> Item -> Task -> Workflow Task -> SharePoint Server Workflow Task ->   Publishing Approval Workflow Task (en-US)

System -> Item -> Task -> Workflow Task -> SharePoint Server Workflow Task ->   Signatures Workflow Task Deprecated

 

 

System ->   Item
System -> Item ->   Announcement
System -> Item ->   Circulation
System -> Item ->   Comment
System -> Item ->   Contact
System -> Item ->   Device Channel
System -> Item ->   Document
System -> Item ->   DomainGroup
System -> Item ->   East Asia Contact
System -> Item ->   Event
System -> Item ->   Folder
System -> Item ->   Health Analyzer Report
System -> Item ->   Health Analyzer Rule Definition
System -> Item ->   Holiday
System -> Item ->   Issue
System -> Item ->   Link
System -> Item ->   Message
System -> Item ->   New Word
System -> Item ->   Official Notice
System -> Item ->   Page Output Cache
System -> Item ->   PerformancePoint Base
System -> Item ->   Person
System -> Item ->   Phone Call Memo
System -> Item ->   Post
System -> Item ->   Published Link
System -> Item ->   Resource
System -> Item ->   Resource Group
System -> Item ->   Reusable HTML
System -> Item ->   Reusable Text
System -> Item ->   Rule
System -> Item ->   SharePointGroup
System -> Item ->   Task
System -> Item ->   Timecard
System -> Item ->   Users
System -> Item ->   What's New Notification
System -> Item ->   Workflow History
System -> Item ->   WorkflowServiceDefinition
System -> Item ->   WorkflowServiceSubscription
System -> Item -> Document ->   Basic Page
System -> Item -> Document ->   Design File
System -> Item -> Document ->   Device Channel Mappings
System -> Item -> Document ->   Display Template
System -> Item -> Document ->   Dublin Core Columns
System -> Item -> Document ->   Form
System -> Item -> Document ->   InfoPath Form Template
System -> Item -> Document ->   JavaScript Display Template
System -> Item -> Document ->   Link to a Document
System -> Item -> Document ->   List View Style
System -> Item -> Document ->   Master Page
System -> Item -> Document ->   Master Page Preview
System -> Item -> Document ->   Office Data Connection File
System -> Item -> Document ->   PerformancePoint Monitoring Document Type
System -> Item -> Document ->   Picture
System -> Item -> Document ->   Report Document
System -> Item -> Document ->   Rich Media Asset
System -> Item -> Document ->   System Master Page
System -> Item -> Document ->   System Page
System -> Item -> Document ->   System Page Layout
System -> Item -> Document ->   Translation Package
System -> Item -> Document ->   Translation Status
System -> Item -> Document ->   Universal Data Connection File
System -> Item -> Document ->   Unknown Document Type
System -> Item -> Document ->   User Workflow Document
System -> Item -> Document ->   Wiki Page
System -> Item -> Document -> Basic Page ->   Web Part Page
System -> Item -> Document -> Display Template ->   Control Display Template
System -> Item -> Document -> Display Template ->   Display Template Code
System -> Item -> Document -> Display Template ->   Filter Display Template
System -> Item -> Document -> Display Template ->   Group Display Template
System -> Item -> Document -> Display Template ->   Item Display Template
System -> Item -> Document -> PerformancePoint Monitoring Document Type ->   PerformancePoint Data Source
System -> Item -> Document -> Rich Media Asset ->   Audio
System -> Item -> Document -> Rich Media Asset ->   Image
System -> Item -> Document -> Rich Media Asset ->   Video Rendition
System -> Item -> Document -> System Master Page ->   ASP NET Master Page
System -> Item -> Document -> System Master Page -> ASP NET Master Page ->   Html Master Page
System -> Item -> Document -> System Page ->   Page
System -> Item -> Document -> System Page -> Page ->   Article Page
System -> Item -> Document -> System Page -> Page ->   Catalog-Item Reuse
System -> Item -> Document -> System Page -> Page ->   Enterprise Wiki Page
System -> Item -> Document -> System Page -> Page ->   Error Page
System -> Item -> Document -> System Page -> Page ->   Redirect Page
System -> Item -> Document -> System Page -> Page ->   Welcome Page
System -> Item -> Document -> System Page -> Page -> Enterprise Wiki Page ->   Project Page
System -> Item -> Document -> System Page Layout ->   Page Layout
System -> Item -> Document -> System Page Layout -> Page Layout ->   Html Page Layout
System -> Item -> Event ->   Reservations
System -> Item -> Event ->   Schedule
System -> Item -> Event ->   Schedule and Reservations
System -> Item -> Folder ->   Discussion
System -> Item -> Folder ->   Document Collection Folder
System -> Item -> Folder ->   RootOfList
System -> Item -> Folder ->   Summary Task
System -> Item -> Folder -> Document Collection Folder ->   Document Set
System -> Item -> Folder -> Document Collection Folder -> Document Set ->   System Media Collection
System -> Item -> Folder -> Document Collection Folder -> Document Set -> System Media Collection ->   Video
System -> Item -> PerformancePoint Base ->   PerformancePoint Dashboard
System -> Item -> PerformancePoint Base ->   PerformancePoint Filter
System -> Item -> PerformancePoint Base ->   PerformancePoint Indicator
System -> Item -> PerformancePoint Base ->   PerformancePoint KPI
System -> Item -> PerformancePoint Base ->   PerformancePoint Report
System -> Item -> PerformancePoint Base ->   PerformancePoint Scorecard
System -> Item -> Task ->   Administrative Task
System -> Item -> Task ->   Workflow Task
System -> Item -> Task ->   Workflow Task (SharePoint 2013)
System -> Item -> Task -> Workflow Task ->   PSWApprovalTask
System -> Item -> Task -> Workflow Task ->   SharePoint Server Workflow Task
System -> Item -> Task -> Workflow Task -> SharePoint Server Workflow Task ->   Approval Workflow Task (en-US)
System -> Item -> Task -> Workflow Task -> SharePoint Server Workflow Task ->   Collect Feedback Workflow Task (en-US)
System -> Item -> Task -> Workflow Task -> SharePoint Server Workflow Task ->   Collect Signatures Workflow Task (en-US)
System -> Item -> Task -> Workflow Task -> SharePoint Server Workflow Task ->   Publishing Approval Workflow Task (en-US)
System -> Item -> Task -> Workflow Task -> SharePoint Server Workflow Task ->   Signatures Workflow Task Deprecated