For those of you that are familiar with the project ideas lists in Microsoft’s PPM PWA application you might want to skip this first paragraph. Any list you create in the PWA site collection at the top level you will see a button Create Projects, if you are not familiar with this feature take a look at this blog post: https://pwmather.wordpress.com/2012/12/13/creating-and-adding-projects-to-projectserver-2013-ps2013-sp2013-office365-part-1/.
The purpose of this post isn’t to revisit that feature, this post covers getting access to some of the data on that list that is hidden from the views and creating an enhanced view for the Project Ideas type list.
If you look at the view details, you can see below the columns I can add to this view:
Yet if I look at the columns available on this list using the REST API I see a few more, a key one being MSPWAPROJUID as seen below:
This column gets updated with the Project GUID when you create a project from the list. As this is a hidden column it can’t be added to any views which is a shame as that would be very useful. I thought ok, simple, I will just update the field hidden property false then add it to the view. Whilst that change is very simple with a few lines of code this appears to break the column getting updated with the Project GUID so I don’t recommend doing that currently. If I found a way to get this working I will create a post. So as that didn’t work that lead me on to the next idea, lets build my own view on a page. This can be seen below:
I have made the Item Title clickable to open the list item in a new window and where an idea item has been converted into a project, the Project GUID is a clickable link to the view the project. This opens the schedule Project Detail Page. The columns are sortable, by default it is sorted by Item ID, to change this use the arrows in the table column heading. As you can see, I don’t have much data on my test system and only one idea has been created into a project.
I have made the code available on the Microsoft code gallery, it can be downloaded here: https://gallery.technet.microsoft.com/Display-Online-ideas-list-c59c8cc7
To get the script to work for your PWA instance in Project Online you will need to update the listName variable to set the correct list title for your project ideas list:
Click Apply then OK and the data should load if the listName variable is correct. You can then add a link to the new page from the PWA quick launch if needed.
A nice simple solution that provides more functionality than the standard SharePoint view.
Tags: PPM, Project 2016, Project Online
Just a quick post to left you know about an update to the Resource Engagements feature activation. When this was released around a year ago in Project Online, it was stated that all Project Online instances would have the feature enabled by September 2016 with the resource plan data migrated. There has been an update to, this date has been delayed for now, see the comment below from the article:
“The feature will no longer be automatically activated on September 22, 2016.”
#ProjectServer and #SharePoint 2010 / 2013 / 2016 July 2016 Cumulative Update #PS2010 #SP2010 #PS2013 #SP2013 #MSProjectJuly 12, 2016 at 7:53 pm | Posted in Administration, CU, Fixes, Functionality, Information | Leave a comment
Tags: Office 2010, Office 2013, Office 2016, Project 2010, Project 2013, Project 2016, Project Server 2010, Project Server 2013, PS2010, PS2013
The Office 2016 July 2016 updates and cumulative updates are now available, please see the links below:
Project 2016 July 2016 update:
The Office 2013 July 2016 updates and cumulative updates are now available, please see the links below:
Project Server 2013 July 2016 CU Server Roll up package:
Project Server 2013 July 2016 update:
Project 2013 July 2016 update:
Also worth noting, if you haven’t done so already, install Service Pack 1 http://support2.microsoft.com/kb/2880556 first if installing the July 2016 CU.
The Office 2010 July 2016 updates and cumulative updates are now available, please see the links below:
Project Server 2010 July 2016 CU Server Roll up package:
Project Server 2010 July 2016 update:
< no update this month>
Project 2010 July 2016 update:
< no update this month>
SP2 is a pre-requisite for the Office 2010 July 2016 updates.
As always, fully test these updates on a replica test environment before deploying to production.
Tags: Office365, PowerShell, PPM, Project Online, Project Server 2013, Project Server 2016
This PowerShell script will use the Project Reporting OData API to get a list of all the Project Sites in the PWA Site Collection linked to a project. It will then access each of those project sites to enable you to easily update / review the site if needed. This example just lists all of the list titles for each site but can be used as a starting script for modifying a particular list or adding a new list on all project sites etc. This could be used to help rollout changes to existing Project Sites, the code here will help you get connected and access each Project Site object using CSOM. You could even use this example to get the project site URLs then use the approach I blogged about the other month with the PnP PowerShell to month the sites. The example is for Project Online but could easily be updated for Project Server 2013 / 2016.
The user running the script will need to update the source PWA instance URL, username and password. The account will need access to the OData API in PWA and access to all of the project sites.
This script example can be downloaded here: https://gallery.technet.microsoft.com/Access-all-Online-Projects-568c7c59
To get the script to work you will need to reference the DLL as seen in the image below:
This can be installed from the SharePoint Online Client components / management shell. I used the dll from the SharePoint Online Management Shell in this example.
Please note, this has only been tested in PowerShell 3.0 and might not work in other versions. If you have any issues try this in PowerShell 3.0.
The good thing about using the OData API to return the list of Project Site URLs is that if you have certain sites for each Enterprise Project Type you could easily filter the OData query to only return the project site URLs for the correct Enterprise Project Type.
Once the variables have been updated correctly, placeholder values seen below:
Save and run the PowerShell script (fully test on a non-production PWA site collection before Production), firstly this example will give you a count of project sites:
Then for each of those sites it will list all of the SharePoint lists on each site:
As mentioned, this just lists all of the lists so probably isn’t that useful unless you wanted to check each Project Site had the correct lists. The script could be modified to update those project sites or lists fairly easily depending on what the changes were. All I would say is that if you are looking to update / make changes to the project sites, fully test your modified script on a non-production PWA instance first as you could cause a lot of damage if you weren’t careful!
The script is provided "As is" with no warranties etc.