SharePoint (and Project Server) Shenanigans

I am a Project Server and SharePoint consultant but my main focus currently is around Project Server. I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011. I am also a certified Prince2 Practitioner. This article has been cross posted from pwmather.wordpress.com (original article)

Something to be aware of when using local master projects in Project Server 2010 or 2013 when tasks in the sub projects have no assignments.

You will see random text / characters next to the Unassigned name as seen below:

The text / characters displayed will change depending on where you last clicked.

Repro steps below:

• Open Project Pro and connect to the server
• Create 1 project, create 3 tasks and assign an enterprise resource to all three tasks, save and publish the project.
• Close and check-in the project
• Create 1 other project, create 3 tasks and assign an enterprise resource to only 2 of the tasks leaving 1 task with no assignment, save and publish the project.
• Close and check-in the project
• Create a new project and insert both of the projects created above as read-only
• Save the master project locally as a file, when prompted hit no to all when prompted to save changes to the two insert projects
• Close the master project and again when prompted hit no to all when prompted to save changes to the two insert projects
• Close Project Pro
• Open Project Pro and connect to the server
• Open the local master project and expand the two inserted projects
• Switch to the Resource Usage view and notice the Unassigned resource name

• Make changes such as expanding the Resource Name column, increase the work etc. and see the Unassigned name update.
• After changing the Resource Name column width:

o Changing work:

o 2013: