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)

This script will enable the users to quick find and navigate to the Project Site for a particular project. This is useful if you have many projects in the instance. The script can be downloaded from the script gallery below:

http://bit.ly/1rMPi1b

To get the script to work you will need to download the following jQuery library: jquery-2.1.1.min.js – jQuery download Another version of this library may work but this was the one I used / tested with. Upload this library to your PWA site collection then update the script file with the correct location. I uploaded this file to the site collection document library as you can see in the code below:

This example script does use the ProjectData API, so users will need access to that for this to work.

Once the script is downloaded, upload this to the PWA site collection, in this example it was uploaded to the site collection documents library. Choose where you want to script to be accessed, in this example I have placed it on the PWA homepage using a content editor web part:

The content link in my example is: /sites/pwa/SiteCollectionDocuments/Project Site Finder.js

Once loaded, the page will look like this:

The user can then type in part of the project name and click “Find Project”:

The Project Site ULR column will contain the associated project site URL with a clickable hyperlink that will open the project site in a new window / new tab.

This only uses intrinsic fields so should work for any Project Online environment but do test it thoroughly first. You might want to improve the error handling etc. before deploying to a production environment. Also remember this does require the user to have access to the ProjectData API for this to work.

The script is provided "As is" with no warranties etc.