Tags: Office365, PPM, Project 2013, Project 2016, Project Online
Following on from the announcement a while back and the details on the Office 365 roadmap, you might see the unique Project ID feature now available on your tenant. The link to the roadmap notification is below:
This feature enables you to create a unique Project ID for each project in a particular Enterprise Project Type (EPT). To access the configuration for the unique ID click PWA Settings > Enterprise Project Types and click on the EPT that you require a unique ID for each project. This is an EPT setting and not a global setting. Once navigated to the EPT page you will see the following section – Project Id:
The starting number and minimum digit padding settings are required but you can also set a prefix and post fix. On my demo environment I set the following:
This feature adds a new default Project ID field as seen on my PDP:
This field is also added to all the default Project Center views such as the Summary view as seen below:
It can be added to new Project Center views too:
The project id is set when the project is created using that EPT, so for existing projects a Project ID will not be set even if you edit it and publish it. The “Pauls Test Project 001” existed before the feature was available on my PWA instance, as you can see this has a blank Project ID field:
You can type an ID in there if needed, for example I manually typed the next number available (00003):
I then created another new project but this duplicated the Project ID as seen below for project “Pauls Test Project 4”:
You can also modify a Project ID that was auto generated, see project “Pauls Test Project number 002” below:
This new field is available in the Odata Reporting API (_api/ProjectData/Projects), it is called ProjectIdentifier as seen below:
It is also available in the JSOM REST API (_api/ProjectServer/Projects) as well:
This is a great new addition to Project Online, just be aware that existing Projects wont get an ID generated and the Project ID can be set / updated manually.
Update multiple #ProjectOnline PWA Instances using c# .Net console app #Office365 #csharpe #PPM #PMOTDecember 23, 2015 at 4:12 pm | Posted in .Net, Add-on, Administration, App, Configuration, Customisation, Functionality, Information | Leave a comment
Tags: .Net, CSOM, Office365, PPM, Project Online, Project Server 2013
Following on from a post I wrote over a month ago regarding checking entities from multiple Project Online PWA instances, this post covers updating multiple Project Online PWA instances. The first post can be found below:
In this post I demonstrate a way in which you can manage configuration across multiple PWA instances, for example you might want to create a new custom field on more than one instance. This is a simple example just to show you the idea. As this is very much an example, I haven’t released any code or solution but you can see the core code further on in the post.
For the purpose of this blog post I created a C# .Net console application. Once you have a new visual studio console app project you will need to add the references to the following DLLs:
I used the v15 SharePoint and Project Server dlls here.
In the program add these dlls:
The first part of the code is to capture the custom field name and description plus the number of PWA instances to update:
It then goes into a loop to create the custom field on the specified PWA site:
The code below is used to secure the password in the console input:
That is it. This example will create a Project level custom field but you could easily update the code to get the user to enter the entity type (task / resource etc.)
To see this in action see below:
Enter the custom field name:
Enter the custom field description:
Enter the number of PWA instances to update:
Enter the first PWA site URL:
Enter the username for an account that has access to create custom fields:
Enter the password for that account:
After pressing enter it will go off and create the custom field on the first PWA instance:
Press any key and it will go back to ask for the 2nd PWA instance:
It will then prompt for the username and password as before. It will keep looping through depending on how many PWA sites needed to be updated.
On one of those PWA instances we can see the field was created:
Nice and easy, saves navigating around multiple PWA site collections for a simple change you might want to roll out across multiple instances.
#ProjectServer and #SharePoint 2010 / 2013 / 2016 December 2015 Cumulative Update #PS2010 #SP2010 #PS2013 #SP2013 #MSProjectDecember 9, 2015 at 7:34 am | 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 December 2015 updates and cumulative updates are now available, please see the links below:
Project 2016 December 2015 update:
The Office 2013 December 2015 updates and cumulative updates are now available, please see the links below:
Project Server 2013 December 2015 CU Server Roll up package:
Project Server 2013 December 2015 update:
Project 2013 December 2015 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 December 2015 CU.
The Office 2010 December 2015 updates and cumulative updates are now available, please see the links below:
Project Server 2010 December 2015 CU Server Roll up package:
Project Server 2010 December 2015 update:
<no specific Project Server 2010 update>
Project 2010 December 2015 update:
SP2 is a pre-requisite for the Office 2010 December 2015 updates.
As always, fully test these updates on a replica test environment before deploying to production.
This script enables you to capture the the team / staff morale each day – your team members just need to click one of the smiley faces:
In the example above I am logged in with the tenant admin account called “admin admin”. When a user clicks one of the icons it creates an item in the “ProjectTeamMorale” list in the PWA site:
If they click the happy faces it sets the item status to Happy, if they click the sad face it sets the status to Unhappy.
This list will need to be created manually with the following details:
List Name: ProjectTeamMorale
The Date column setting defaults to Today:
Once the list is set up the script can be added to the PWA homepage using a content editor web part:
That is it. The script can easily be updated to use different images or include more than two statuses etc. In this example I have done this for PWA but this could be added to a SharePoint intranet site to capture the staff members morale rather than just the project team in this example.
You can then generate a report to view the team / staff morale over time.
Try it out 🙂