Project workspaces are awesome. There I have said it. But one thing that has always frustrated me and other users is how hard it is to determine what project the workspace is linked to. The only reliable way of determining the ProjectUID is to look in the Property Bag of the site where Project Server stores the association. There are a couple of tricks that will let you find out the ProjectUID, one of them being developing a custom web part like I did a while back, or using the CSOM in 2013 as Giles Hamson posted a while ago,

Recently I have seen this problem manifest itself at two customers, so I thought I would post about it to save anyone else running into it, or scratching their heads. When you customise project workspaces, or SharePoint workspaces in general, you have two options to remove the web parts from the page: Close the web part – this stops the web part being rendered on the page, but still being created on each page load Delete the web part – this removes the web part from the page completely.

Every now and again whilst using the Project Server Demo and Evaluation pack, I run into an ‘File Not Found ‘ error when clicking on a risk or issue in a project workspace. On investigation in the ULS logs, the actual error is: The important part of the error message that gives away what the problem is is the ‘http://moss.contoso.com/pwa’, which is not the site we are using, but it is the site the workspace is looking at to get the risk or issue form.

It’s always puzzled me why Microsoft never did show the ID of a SharePoint based list entry in the edit or display form. What do I mean by that? Well, out of the box, when you create a list in SharePoint, each item has an ID associated. This ID is then used to identify the individual records in the list. Once you have created an item in the list you can see the ID in the view

There was a post in the Project forums a few weeks ago from a user asking how to undelete a project workspace that had been deleted accidently. Project Server provides functionality that allows enterprise objects including projects, calendars & resource pools to be backed up and subsequently restored, but this capability does not cover project workspaces. As workspaces are stored within a SharePoint site collection, it is necessary to use SharePoint backup and restore techniques to get the workspace back.