#ProjectOnline reporting on task Predecessors and Successors #O365 #MSProject #PPM #PMOT # Excel #PowerBI #OData

October 13, 2018 at 9:23 am | Posted in Administration, Configuration, Customisation, Fixes, Functionality, Information, Reporting | 3 Comments
Tags: , , , ,

A few times I have heard this topic come up so I thought it was worth a quick blog post to give two examples for getting access to this detail. Firstly a quick look at my sample project to see the data and task links:

image

As we can see, all tasks are linked. The predecessor and successor details are not available in the OData reporting API by default: ({PWASiteURL}/_api/ProjectData).

The first option we will explore is using the REST CSOM API ({PWAURL}/_api/ProjectServer). To access this is not a simple read from one endpoint like it would be in the OData reporting API if the data was there. When using the CSOM REST API you have to first get the project then from there you can get the task details and task link details. Below we walkthrough this process and view the results. I am just using the browser to return the data for ease. Let’s have a look at this Project data using: {PWASiteURL}/_api/ProjectServer/Projects(‘a28bf087-2acb-e811-afb0-00155d143a0e’) where the GUID is the project GUID for the project seen above. This returns:

SNAGHTML1271759a

Here you can see all of the related endpoints and then the project properties below. I have outlined in red the two related endpoints that are useful to us, the TaskLinks and Tasks.

Lets have a look at the TaskLinks first – we have 4 links in the simple plan displayed above, this matches what we see in the TaskLinks endpoint:

{PWASiteUrl}/_api/ProjectServer/Projects(‘a28bf087-2acb-e811-afb0-00155d143a0e’)/TaskLinks

SNAGHTML127510a3

For each link we can then access two other endpoints /End and /Start and see two properties for the link, Id and DependencyType. Id is the TaskLink Id and DependencyType is the internal dependency type value, the enumerations for the dependency type can be found here: https://msdn.microsoft.com/en-us/library/microsoft.projectserver.client.dependencytype_di_pj14mref.aspx. Looking at the data returned, I have 3 links with a dependency type of 1 (Finish to Start) and 1 link with a dependency type of 3 (Start to Start). Now for one of those TaskLinks, we will look at what the /End and /Start endpoints provide. I will use the TaskLink with a Start to Start dependency type for this. Firstly the /Start endpoint:

{PWASiteUL}/_api/ProjectServer/Projects(‘a28bf087-2acb-e811-afb0-00155d143a0e’)/TaskLinks(‘0d7da2b3-2dcb-e811-9328-1002b5489337’)/Start – where the 2nd GUID is the TaskLink GUID

SNAGHTML1283a2ae

This returns all of the data for the starting task, in this example it is task T2 (I’ve updated the REST call to just return the task name:

SNAGHTML12872358

Task T2 is the task starting the link as seen in the project plan:

image

The /End endpoint, as you can guess will return the same details but for the task ending the link:

{PWASiteUL}/_api/ProjectServer/Projects(‘a28bf087-2acb-e811-afb0-00155d143a0e’)/TaskLinks(‘0d7da2b3-2dcb-e811-9328-1002b5489337’)/End – where the 2nd GUID is the TaskLink GUID – I’ve update the REST call to just return the task name:

SNAGHTML128b4ce6

This returns T3 from the example project:

image

As you can see, using the TaskLinks endpoint once we have the project, we can then navigate to find the task details for the linked tasks.

Now lets look at what the /Tasks endpoint can do for us to find the linked tasks. Accessing the {PWASiteUrl}/_api/ProjectServer/Projects(‘a28bf087-2acb-e811-afb0-00155d143a0e’)/Tasks endpoint will return all of the tasks in the project (based on the project GUID used in the REST call):

SNAGHTML128ffcaa

For each task in the project we can see the task properties but also navigate to another endpoint to view more related data for that one task. For example, we can then navigate and view the /Predecessors and /Successors. I will use task T3 for this walkthrough by passing in the Task GUID for T3. Accessing the predecessors data for task T3:

{PWASiteUrl}/_api/ProjectServer/Projects(‘a28bf087-2acb-e811-afb0-00155d143a0e’)/Tasks(‘b3433ba7-2dcb-e811-9328-1002b5489337’)/Predecessors – where I have passed in the task GUID for T3:

SNAGHTML12964d6d

This returns the TaskLink details for the predecessor task – from that point we can then use the /End and /Start related queries to get the linked task details. The same goes for the /Successors endpoint for the example task T3:

{PWASiteUrl}/_api/ProjectServer/Projects(‘a28bf087-2acb-e811-afb0-00155d143a0e’)/Tasks(‘b3433ba7-2dcb-e811-9328-1002b5489337’)/Successors – where I have passed in the task GUID for T3:

SNAGHTML129abb66

This returns the TaskLink details for the successor task – from that point we can then use the /End and /Start related queries to get the linked task details.

As you can see, trying the get that data for all linked tasks in a report using Power Query wouldn’t be a simple query to one endpoint but it is possible to follow it through to get the data needed.

The next option to look at is creating two task level calculated fields so that you can get the predecessor and successor details in the /Tasks endpoint in the OData reporting API ({PWASiteURL}/_api/ProjectData/Tasks). Whilst this is simplifies the reporting experience there is a performance cost to this – certainly for large projects with many tasks. Also this will use 2 of the recommended maximum 5 task level calculated fields! In PWA Settings > Enterprise Custom Fields and Lookup Tables, create two new Task level text fields that use formulas, one field will be for predecessors and one for successors. In the predecessors field formula use [Predecessors] and in the successors field formula use [Successors]. The predecessors custom field can be seen below:

image

The next time you publish your project/s you will then see the data available in the OData Reporting API:

{PWASiteUrl}/_api/ProjectData/Projects(guid’a28bf087-2acb-e811-afb0-00155d143a0e’)/Tasks?$Select=TaskName,TaskPredecessors,TaskSuccessors

SNAGHTML12a6e5c7

Hope that helps!

Advertisements

#ProjectOnline Export Capacity Planning data to #Excel issue #PPM #PMOT #Office365 #MSProject

June 30, 2018 at 7:44 am | Posted in Administration, Configuration, Fixes, Functionality, Information, Issue | Comments Off on #ProjectOnline Export Capacity Planning data to #Excel issue #PPM #PMOT #Office365 #MSProject
Tags: , , ,

Just a quick post to highlight an issue I came across that I thought might be worth posting about in case anyone else runs into the same issue. In Project Online, in PWA you can export most of the grids to Excel. I was testing something in PWA and came across an issue exporting the Capacity Planning grid to Excel, I clicked the button but nothing happened, the details grid would flicker when the button was clicked but nothing after that. Opened the browser debugger and tried again, no console errors but looking at the Network log an error 500 was thrown for the ProjectServer.svc:

SNAGHTML57ccc6b

Looking at the response I could see a general unhandled exception was thrown caused by a key not being present in the dictionary:

image

Looking at the request payload I could see two resource GUIDs were included:

image

Looking at the grid data there was only one resource present:

image

Looking back in the Resource Center, I did have two resources selected:

SNAGHTML586d081

One being a Cost resource, I deselected the Capex resource and tried the Export to Excel from the Capacity Planning page and all worked as expected.

If you do run into the issue with exporting the Capacity Planning grid to Excel, check the resource types you have selected, deselect Cost and Material resources then try again and hopefully that will resolve the issue for you. I will mention this to the Project team at Microsoft to see if this is something they are already aware of.

#ProjectServer and #SharePoint 2013 / 2016 June 2018 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject

June 14, 2018 at 7:33 pm | Posted in Administration, Configuration, CU, Fixes, Functionality, Information | Comments Off on #ProjectServer and #SharePoint 2013 / 2016 June 2018 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject
Tags: , , , , , , ,

The Office 2016 June 2018 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4299875

Project 2016 June 2018 update:
https://support.microsoft.com/en-us/kb/4022164

SharePoint Server 2016 / Project Server 2016 June 2018 update: 
https://support.microsoft.com/en-us/kb/4022173 & https://support.microsoft.com/en-us/kb/4022178

The Office 2013 June 2018 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4299875

Project Server 2013 June 2018 CU Server Roll up package:
https://support.microsoft.com/en-us/kb/4022185

Project Server 2013 June 2018 update:
https://support.microsoft.com/en-us/kb/4022192

Project 2013 June 2018 update:
https://support.microsoft.com/en-us/kb/4022171

Also worth noting, if you haven’t done so already, install Service Pack 1 http://support2.microsoft.com/kb/2880556 first if installing the June 2018 CU for 2013.

As always, fully test these updates on a replica test environment before deploying to production.

#ProjectServer and #SharePoint 2013 / 2016 May 2018 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject

May 11, 2018 at 10:06 am | Posted in Administration, Configuration, CU, Fixes, Functionality, Information, Installation | Comments Off on #ProjectServer and #SharePoint 2013 / 2016 May 2018 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject
Tags: , , , , , , ,

The Office 2016 May 2018 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4133083

Project 2016 May 2018 update:
https://support.microsoft.com/en-us/kb/4018373

SharePoint Server 2016 / Project Server 2016 May 2018 update: 
https://support.microsoft.com/en-us/kb/4018386 & https://support.microsoft.com/en-us/kb/4018381

The Office 2013 May 2018 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4133083

Project Server 2013 May 2018 CU Server Roll up package:
https://support.microsoft.com/en-us/kb/4018395

Project Server 2013 May 2018 update:
https://support.microsoft.com/en-us/kb/4022130

Project 2013 May 2018 update:
https://support.microsoft.com/en-us/kb/4018379

Also worth noting, if you haven’t done so already, install Service Pack 1 http://support2.microsoft.com/kb/2880556 first if installing the May 2018 CU for 2013.

As always, fully test these updates on a replica test environment before deploying to production.

#ProjectServer and #SharePoint 2013 / 2016 April 2018 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject

April 11, 2018 at 6:26 am | Posted in Administration, Configuration, CU, Customisation, Fixes, Functionality, Information, Installation | Comments Off on #ProjectServer and #SharePoint 2013 / 2016 April 2018 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject
Tags: , , , , , , ,

The Office 2016 April 2018 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4098622

Project 2016 April 2018 update:
https://support.microsoft.com/en-us/kb/4018320

SharePoint Server 2016 / Project Server 2016 April 2018 update: 
https://support.microsoft.com/en-us/kb/4018340 & https://support.microsoft.com/en-us/kb/4018336

The Office 2013 April 2018 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4098622

Project Server 2013 April 2018 CU Server Roll up package:
https://support.microsoft.com/en-us/kb/4018346

Project Server 2013 April 2018 update:
https://support.microsoft.com/en-us/kb/4018352

Project 2013 April 2018 update:
https://support.microsoft.com/en-us/kb/4018335

Also worth noting, if you haven’t done so already, install Service Pack 1 http://support2.microsoft.com/kb/2880556 first if installing the April 2018 CU for 2013.

As always, fully test these updates on a replica test environment before deploying to production.

#ProjectServer and #SharePoint 2013 / 2016 March 2018 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject

March 16, 2018 at 6:22 pm | Posted in Administration, CU, Fixes, Functionality, Information, Installation | Comments Off on #ProjectServer and #SharePoint 2013 / 2016 March 2018 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject
Tags: , , , , , , ,

The Office 2016 March 2018 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4090988

Project 2016 March 2018 update:
https://support.microsoft.com/en-us/kb/4011734

SharePoint Server 2016 / Project Server 2016 March 2018 update: 
https://support.microsoft.com/en-us/kb/4018293 & https://support.microsoft.com/en-us/kb/4011687

The Office 2013 March 2018 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4090988

Project Server 2013 March 2018 CU Server Roll up package:
https://support.microsoft.com/en-us/kb/4018301

Project Server 2013 March 2018 update:
https://support.microsoft.com/en-us/kb/4018305

Project 2013 March 2018 update:
https://support.microsoft.com/en-us/kb/4018292

Also worth noting, if you haven’t done so already, install Service Pack 1 http://support2.microsoft.com/kb/2880556 first if installing the March 2018 CU for 2013.

As always, fully test these updates on a replica test environment before deploying to production.

#ProjectOnline workaround for Project app link on #O365 waffle app launcher #PPM #PMOT #Office365

March 8, 2018 at 2:42 am | Posted in Administration, App, Configuration, Customisation, Fixes, Functionality, Information | 2 Comments
Tags: , , ,

For organisations that only have one Project Web App (PWA) instance and use /PWA, today using the Project app link on the Office 365 waffle app launcher works as expected. For those organisations that have multiple PWA instances this can be an issue. The link I am talking about can be seen below:

SNAGHTMLc747618

This points to /MyProjects as seen above but when Project Online is present on the tenant it will always redirect to /sites/PWA as seen below:

SNAGHTMLc7422f6

This can be a problem for those customers that either have multiple PWA instances or do not use the default /PWA instance. Unfortunately the Project link on the waffle app launcher is not configurable so one workaround we have done for clients before is to not use the /PWA instance at all apart from using it as a landing page for the other PWA instances in the organisation. If you are in the planning stage for rolling out Project Online and know that you will have multiple PWA instances on the same Office 365 tenant, this might be a good option for you to consider and explore.

Firstly create the following css file that will be used to remove the PWA quick launch menu:

image

Save this on the /PWA site somewhere such as the Style Library:

image

Now edit the PWA homepage and delete the “Track your work” web part and add a content editor web part, in the content editor web part reference the .css file and change the chrome type to None:

SNAGHTMLc73b0f3

Click Apply then click OK and the quick launch will disappear. Add another content editor web part and update the Title to “Project Web App sites” or a more appropriate name as required:

image

Click the new content editor web part where is states click here to add new content then add in the links to all the PWA instances that you have on the tenant using the content editor web part controls – you have lots of options and can make it look as nice as you like. In this example I have just used a simple table:

image

Click Stop editing on the Page tab and you will see the following:

image

Then ensure all users of Project Online have read access to the /PWA site (do not grant higher access as you do not want them incorrectly creating projects here):

image

This way if a user clicks the “Project” app link on the Office 365 waffle app launcher they can at least then easily navigate onto the correct PWA instance.

You could take this even further and have multiple content editor web parts on the page, one for each PWA instance then use SharePoint’s audience targeting feature to show the correct PWA instance/s for the logged on user.

#ProjectServer and #SharePoint 2013 / 2016 February 2018 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject

February 14, 2018 at 7:39 am | Posted in Administration, CU, Fixes, Functionality, Information, Installation | Comments Off on #ProjectServer and #SharePoint 2013 / 2016 February 2018 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject
Tags: , , , , , , ,

The Office 2016 February 2018 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4077965

Project 2016 February 2018 update:
https://support.microsoft.com/en-us/kb/4011672

SharePoint Server 2016 / Project Server 2016 February 2018 update: 
https://support.microsoft.com/en-us/kb/4011680

The Office 2013 February 2018 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4077965

Project Server 2013 February 2018 CU Server Roll up package:
https://support.microsoft.com/en-us/kb/4011694

Project Server 2013 February 2018 update:
https://support.microsoft.com/en-us/kb/4011701

Project 2013 February 2018 update:
https://support.microsoft.com/en-us/kb/4011679

Also worth noting, if you haven’t done so already, install Service Pack 1 http://support2.microsoft.com/kb/2880556 first if installing the February 2018 CU for 2013.

As always, fully test these updates on a replica test environment before deploying to production.

#ProjectServer and #SharePoint 2013 / 2016 January 2018 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject

January 13, 2018 at 9:13 am | Posted in Administration, CU, Fixes, Functionality, Information, Installation | Comments Off on #ProjectServer and #SharePoint 2013 / 2016 January 2018 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject
Tags: , , , , , , ,

The Office 2016 January 2018 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4058103

Project 2016 January 2018 update:
https://support.microsoft.com/en-us/kb/4011633

SharePoint Server 2016 / Project Server 2016 January 2018 update: 
https://support.microsoft.com/en-us/kb/4011642 & https://support.microsoft.com/en-us/kb/4011645

The Office 2013 January 2018 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4058103

Project Server 2013 January 2018 CU Server Roll up package:
https://support.microsoft.com/en-us/kb/4011650

Project Server 2013 January 2018 update:
https://support.microsoft.com/en-us/kb/4011654

Project 2013 January 2018 update:
https://support.microsoft.com/en-us/kb/4011640

Also worth noting, if you haven’t done so already, install Service Pack 1 http://support2.microsoft.com/kb/2880556 first if installing the January 2018 CU for 2013.

As always, fully test these updates on a replica test environment before deploying to production.

#ProjectServer and #SharePoint 2013 / 2016 November 2017 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject

November 16, 2017 at 9:20 am | Posted in Administration, CU, Fixes, Functionality, Information, Installation | Comments Off on #ProjectServer and #SharePoint 2013 / 2016 November 2017 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject
Tags: , , , , , , ,

The Office 2016 November 2017 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4051890

Project 2016 November 2017 update:
https://support.microsoft.com/en-us/kb/4011227

SharePoint Server 2016 / Project Server 2016 November 2017 update: 
https://support.microsoft.com/en-us/kb/4011243 & https://support.microsoft.com/en-us/kb/4011244

The Office 2013 November 2017 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/4051890

Project Server 2013 November 2017 CU Server Roll up package:
https://support.microsoft.com/en-us/kb/4011249

Project Server 2013 November 2017 update:
https://support.microsoft.com/en-us/kb/4011257

Project 2013 November 2017 update:
https://support.microsoft.com/en-us/kb/4011235

Also worth noting, if you haven’t done so already, install Service Pack 1 http://support2.microsoft.com/kb/2880556 first if installing the November 2017 CU for 2013.

As always, fully test these updates on a replica test environment before deploying to production.

Next Page »

Create a free website or blog at WordPress.com.
Entries and comments feeds.