SharePoint 2013 – Restoring the 2010 Navigate Up Crumb Trail Button

 

2007

SharePoint 2007 had the nice complete "bread crumb trail" across the top of every page:

   

2010

SharePoint 2010 removed those and gave us a very limited, library relative, crumb trail which has gaps if too long:

   

As a compromise, 2010 gave us a little button / dropdown called Navigate up to make up for the missing crumb trail:

 

2013

What Microsoft giveth, Microsoft takes away. No more crumb trails in 2013!  I think 2013 users are supposed to only "Follow" or search for sites. :-)

Actually… the Navigate up button is still there, but it's been hidden! It's just between the site logo and the Top Link Bar. All you need to do is make two quick changes to your master page, and the crumb trail is back!

In the example below I'm in a subsite named Sales Training and I've drilled down into a library with a bunch of folders looking for the 2014 schedules. In two clicks I can quickly jump up to a higher level folder, library or site.

Site with the restored Navigate Up button:

   

 

Get back the crumb trail!

The steps:

1. Open your site in SharePoint Designer 2013.
2. In the left panel click Master Pages.
3. Click your master page (probably Seattle.Master for a typical Team Site).
4. Click Edit File.
5. Search for "breadcrumbdropdown".
   
   (If you don't find it, you may be working with a customized or branded master page.)
6. Make two edits…
1. In the line above change display:none to display:inline
2. Two lines down change Visible="false" to Visible="true"
7. Save the master page, and if prompted, click Yes.
8. Return to your site and refresh the page!

 

.

Cincinnati SPUG – 6/26 – Paul Stork Speaking about Yammer

 

Next meeting: June 26th, 2014    Please register at TechLife Cincinnati

Topic:  Yammer

One of the biggest investments Microsoft made in SharePoint 2013 was in the area of "Social" collaboration.  Yet, just before SharePoint 2013 launched Microsoft announced that they had purchased Yammer, another popular "Social" collaboration system.  Since then Microsoft has announced a road map to integrate the cloud based Yammer functionality into both SharePoint Online (Office 365) and traditional SharePoint on-premises. In this talk we will examine the questions
  - What is Yammer? 
  - How is it different from SharePoint "Social" features?
  - How do I use it?
  - What is the state of integration available today for both Office 365 and SharePoint On-premises?

Speaker:  Paul Stork

Paul Stork is a Microsoft SharePoint MVP and MCM who works as a Principal Architect at Blue Chip Consulting based in Cleveland.  He has an MBA from the Weatherhead School of Management and holds a myriad of Microsoft certifications including being a SharePoint 2013 Solutions Expert, Systems Engineer, Solutions Architect, Developer, Database Admin, IT Professional and Professional Developer.  He is an author and/or contributor on several SharePoint books and is a well-known contributor to the SharePoint community. 

And of course... there will be food, door prizes and networking!

We've got books, gadgets and toys! 

http://www.CincinnatiSPUG.org

Merging Two PowerShell Collections into One Output

 

In SharePoint users and groups are both security principles, and both share some common properties. One property, ID, is interesting as it is unique and never duplicated between the lists of users and group. I.e. if there is a user with an ID of 5 then there is never a group with an ID of 5.

In PowerShell there are two separate properties for users and groups, but I wanted to merge the two into one sorted list. Turns out, as long as both Select statements return columns with the same names, then they can be "added" to get a merged result.

 

Example: Users and Groups

$users = $web.SiteUsers | Select Id, Name
$groups = $web.Groups | Select Id, Name
$users + $groups | Sort Id

If you wanted to do it all in one line, then use a few parentheses:

($web.SiteUsers | Select Id, Name)  +  ($web.Groups | Select Id, Name) | Sort Id

What if the column names don't match (but have similar data types)? You will need to create a PowerShell custom column. In the example below I wanted to use the user's DisplayName property instead of the Name property so I had to create a custom column named "Name" to match the "Name" property in the groups Select.

$users = $web.SiteUsers | Select Id, @{Label="Name"; Expression={$_.DisplayName|}}

$groups = $web.Groups | Select Id, Name

$users + $groups | Sort Id

 

.

SharePoint Check Out and Check In Issues

 

As I work to complete my SharePoint security book (only three years so far), I've been testing just about every combination of permissions looking for benefits and side effects. While working on a custom permission level with minimum permissions for an Add, Edit but not Delete user I ran into some interesting issues with Check Out and Check In.

Access Denied… You would think that Check Out and Check In are core document management features that would be available to any user who can edit a document. Turns out two unlikely permissions are needed: Browse User Information and Use Remote Interfaces.

 

Access Denied when checking in a document. (2010 and 2013 on prem and 365)

  

Solution:

User must have the Browse User Information permission to check in files! (This is included in the Contribute permission level.)

This one is certainly not obvious, and could be an issue if you removed this permission to hide the ability to view other users in the site.

 

Access Denied when checking out a document (2010)

Solution:

User must have the Use Remote Interfaces permission to check out files! (This is included in the Contribute permission level.)

This one is certainly not obvious, and could be an issue if you removed this permission to hide the ability to view other users in the site.

Looks like Microsoft made a change in SharePoint 2013 so that this one is no longer an issue.

 

.