Want to capture the last logon time for the #ProjectOnline PWA users? #PPM #JavaScript #Office365 #SharePoint

September 30, 2016 at 2:19 pm | Posted in Add-on, Administration, Configuration, Customisation, Functionality, Information, Reporting | Leave a comment
Tags: , , , ,

This is a supporting blog post for a new JavaScript file I have published to the Microsoft Gallery, it can be downloaded here:

https://gallery.technet.microsoft.com/Capture-Online-user-last-43621a21

Microsoft recently removed the Last Logon details from the Manage Users page in PWA settings for Project Online – Microsoft’s PPM tool. This simple script is an alternative solution that will capture the last logon for the Project Web App users. It wont capture the last logon from Project Professional or if a user accesses the API’s etc., it will only capture the last logon from the page the script is added to. In this example I have added the script to the homepage, so if a user has the Project Center saved as a favourite link and bypasses the PWA homepage then their logon would not be captured. You could add the script to multiple PWA pages if required.

When a user accesses the PWA homepage for the first time that day, an item is created on the SharePoint list in the PWA site, it only captures the logon once per day. See an example on my demo instance:

image

It captures the user name, the logon data and the browser that was used. This list will need to be created manually with the following details:

List Name: PWAUsageList

Columns:

image

The LogonDate column setting defaults to Today:

image

Once the list is set up, upload the JavaScript file to a library on the PWA site then the script can be added to the PWA homepage using a content editor web part:

image

Reference the location of the PWAUsage.js file – in this example I added the JavaScript file to the Shared Document library in the PWA site, also notice the Chrome Type is set to None so nothing is visible on the PWA homepage.

That is it, it will now capture the users who access the PWA homepage. Once you have the data on the list you can then create a report for that data. I will publish a blog post in the next week or so that details this but for now here is an example report screen shot in Power BI:

image

Fully test this on a non-production PWA instance before rolling out to Production, the script is provided As Is with no warranties etc. Try it out and let me know what you think.

#Office365 Project Time Reporter mobile app for #iOS released #ProjectOnline #PPM #Timetracking

September 21, 2016 at 10:49 am | Posted in Add-on, Administration, App, Functionality, Information, Mobile | Leave a comment
Tags: , , , , ,

Yesterday saw the release of the Office 365 Project Time Reporter mobile app for Apple’s iOS, see the announcement here: https://blogs.office.com/2016/09/20/announcing-the-availability-of-office-365-project-time-reporter/

This post gives a walkthrough on getting started and using the app on your iOS device. Firstly download the app for your iOS device from the Apple store:

appstore

Once completed locate the Project Time Reporter app:

app icon

On first launch you will be required to enter the Project Online PWA URL:

splashscreen

You will then see the login screen:

login

Enter your Office 365 credentials and click Sign In and you will see the loading screen briefly whilst the data is loaded:

loading

Once completed you will see the Timesheet for this period:

timeesheet

From here you can enter the actuals as needed. Using the green control menu at the bottom of the app you can scroll between timesheet periods using the previous and next buttons, add a row, save the timesheet, send the timesheet or filter the projects. Using the ellipsis in the top right hand corner you can access other timesheet options such as refresh, go to current period, summary, send progress for all tasks or manage timesheets. The app menu in the top left corner enables you to access the app settings, here you can switch to the tasks view or see the app settings. Below you will see screen shots of some of these features.

Firstly the app menu screen, here you can view Timesheet, Tasks or Settings:

app menu

On Settings you can view the PWA URL and username and turn on two options:

app settings

I turned on the planned time in my app:

timesheet with planned work

To enter time just click in the box for the day you want to add time to:

timesheet actuals

You can use the Save button on the green menu at the bottom of the app to save the timesheet or send the timesheet using the send button. If you have many projects on the current timesheet you can using the filter option:

filter projects

If you want to send progress, click the ellipsis in the top right corner:

timesheet options

Here you will also see other options such as Summary:

timesheet summary

Manage Timesheets:

manage timesheets

On the timesheet view you can add rows using the Add button on the green menu:

add row in TS

We have focused on the Timesheet view here but there is also a Tasks view that is accessible from the app menu > Tasks:

tasks

You can change the view by clicking the Current Tasks heading:

task views

You can access the task options to filter and sort the tasks using the ellipsis in the top right hand corner:

task options

Selecting a task will take you to the task details screen:

taskscreen

To edit a task click Edit in the top right hand corner:

edittasks

Make any changes as needed and click Save or Send.

Download it today and see what you think – it will make the timesheet / task update process so easy when you are on the move!

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

September 14, 2016 at 8:36 am | Posted in Administration, CU, Fixes, Functionality, Information | Leave a comment
Tags: , , , , ,

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

https://support.microsoft.com/en-gb/kb/3188548

Project 2016 September 2016 update:
https://support.microsoft.com/en-gb/kb/3118266

SharePoint Server 2016 September 2016 update – Project Server 2016 fixes:
https://support.microsoft.com/en-gb/kb/3118289 & https://support.microsoft.com/en-gb/kb/3118295

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

https://support.microsoft.com/en-gb/kb/3188548

Project Server 2013 September 2016 CU Server Roll up package:
https://support.microsoft.com/en-gb/kb/3118274

Project Server 2013 September 2016 update:
https://support.microsoft.com/en-gb/kb/3118285

Project 2013 September 2016 update:
https://support.microsoft.com/en-gb/kb/3115493

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

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

https://support.microsoft.com/en-gb/kb/3188548

Project 2010 September 2016 update:
https://support.microsoft.com/en-gb/kb/3115249

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

Error creating Project Sites from custom site template in #ProjectOnline / #SharePoint Online #PPM #Office365

September 1, 2016 at 4:30 pm | Posted in Administration, Configuration, Customisation, Fixes, Functionality, Information, Issue, Workarounds | Leave a comment
Tags: , , , , ,

A quick post, if you are finding that all of a sudden your project sites are failing to create with the error below:

CreateWssSiteContent: Creating project site failed! Project Uid= <site details> Microsoft.SharePoint.SPException: The site template requires that the Feature {e995e28b-9ba8-4668-9933-cf5c146d7a9f} be activated in the site collection. at Microsoft.SharePoint.Utilities.SPUtility.ThrowSPExceptionWithTraceTag

Chances are you using a custom site template and this stopped working within the last week or so. The feature ID SharePoint is complaining about is a “MobileExcelWebAccess” feature. This can’t just be enabled.

The fix is straightforward, locate the site which you used to create the site template and save that site as a template again with a different name / version then link this to the Enterprise Project Type/s. Repeat this for all custom site templates.

#ProjectOnline data capture / snapshot capability with #PowerShell #SharePoint #Office365 #PPM #BI

August 26, 2016 at 11:03 am | Posted in Add-on, Administration, Configuration, Customisation, Functionality, Information, PowerShell, Reporting | 1 Comment
Tags: , , , , , ,

This blog post will show an option to capture Microsoft’s PPM Project Online data into a SharePoint list on a schedule to enable time driven data capture for snapshot / trend reporting capability. This example makes use of a PowerShell script I created to get the data and write this to a SharePoint list. The PowerShell script will use the Project Reporting OData API to get all of the specified project data in the PWA Site Collection then create a list item on the specified SharePoint list. The user setting up the script will need to update the source PWA instance URL, username, password and list name. The account specified will need access to the OData API in PWA and contribute access to the target SharePoint list. The SharePoint list will also need to be created beforehand with the required columns. The OData query will need to be updated to include the correct project level fields required and the part of the script that creates the list items will need to be updated too. This is covered below.

This script example can be downloaded here: https://gallery.technet.microsoft.com/Online-Snapshot-example-0437b680

To get the script to work you will need to reference the DLL as seen in the image below:

image

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.

Firstly decide what project level fields you want to capture, this will determine the list column requirements. Then create the SharePoint list in the PWA site collection with the required columns, for this example I created a list called ProjectSnapShots with the columns below:

image

The SnapshotDate column was set to have today as the default value so that when the items are created the date is set automatically.

Update the Project OData query to include the correct fields that you want to capture, in this simple example I have included the following:

image

$url = $PWAInstanceURL + "/_api/ProjectData/Projects()?`$Filter=ProjectType ne 7&`$Select=ProjectId,ProjectName,ProjectPercentCompleted,ProjectHealth,ROI,RiskRating&`$orderby=ProjectName"

As you can see I have a list column for each project level field. The next part of the script that needs to be updated is the item creation:

image

This is where you map the project level fields to the correct SharePoint list columns based on the data you are capturing.

Also ensure the variables have been updated correctly, placeholder values seen below:

image

Save and run the PowerShell script (fully test on a non-production PWA site collection before Production) to ensure the data is captured correctly in the target SharePoint list. You could then set this up to run as a scheduled task on a local server or a scheduled WebJob in Azure to capture the data weekly or monthly etc. For details on a scheduled WebJob see: https://azure.microsoft.com/en-gb/documentation/articles/web-sites-create-web-jobs/

Once the script is run you will see the data in the SharePoint list, below I have run this 3 times:

image

You could then create a snapshot / trend report as required from the list data and even join to the live Project OData API if you capture the Project ID as I have in the example script / list.

A simple time driven data capture to enable snapshot / trending reports for Project Online. This script could easily be modified to capture the data into a SQL database, either on-prem or in Azure SQL if required. Also if this was to be run in production the script should be updated for error handling with try / catch blocks etc.

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

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

August 9, 2016 at 8:28 pm | Posted in Administration, CU, Fixes, Functionality, Information | Leave a comment
Tags: , , , , ,

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

https://support.microsoft.com/en-gb/kb/3181038

Project 2016 August 2016 update:
https://support.microsoft.com/en-gb/kb/3115424

SharePoint Server 2016 August 2016 update – Project Server 2016 fixes:
https://support.microsoft.com/en-gb/kb/3115437 & https://support.microsoft.com/en-gb/kb/3115441

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

https://support.microsoft.com/en-gb/kb/3181038

Project Server 2013 August 2016 CU Server Roll up package:
https://support.microsoft.com/en-gb/kb/3115448

Project Server 2013 August 2016 update:
https://support.microsoft.com/en-gb/kb/3115456

Project 2013 August 2016 update:
https://support.microsoft.com/en-gb/kb/3115434

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

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

#ProjectOnline / SharePoint CSOM updated to include Resource Engagements #Office365 #SharePointOnline

August 8, 2016 at 2:33 pm | Posted in Add-on, Administration, Configuration, Customisation, Functionality, Information | Leave a comment
Tags: , , ,

Just a quick post to highlight the latest SharePoint Online / Project Online CSOM version (16.1.5521.1200) now includes the Resource Engagement classes and properties:

image

http://dev.office.com/blogs/new-sharepoint-csom-version-released-for-Office-365-august-2016

#ProjectOnline #PowerBI report with hyperlinks #Office365 #PPM #SharePoint #PowerQuery #BI

August 5, 2016 at 12:43 pm | Posted in Administration, Configuration, Customisation, Functionality, Information, Reporting | Leave a comment
Tags: , , , , , ,

In this post we will look at creating a very basic Power BI report that includes hyperlinks to various entities in Microsoft’s Office 365 PPM Project Online PWA site. The report created here will be purely to show you how to create links to the Project Site, Project Detail Page, Issues and Risks items.

Firstly I will create my OData URLs I need for my datasets, these can be seen below:

  • Projects: <PWA site URL>/_api/ProjectData/Projects()?$filter=ProjectType ne 7
  • Issues: <PWA site URL>/_api/ProjectData/Issues
  • Risks: <PWA site URL>/_api/ProjectData/Risks

Now launch the Power BI desktop and click Get Data > OData Feed as seen below:

image

Enter the Projects URL and click OK:

image

On the next screen click Edit:

image

In the Query Editor window click Choose Columns:

image

In the Choose Columns window, uncheck all of the columns – quickest way is the uncheck Select All Columns:

image

Now select the following columns: ProjectId, ProjectName, ProjectWorkspaceInternalUrl

Click OK and the query will only contain those columns:

image

Rename ProjectName to “Project Name” and ProjectWorkspaceInternalUrl to “Project Site URL”, this is done by right clicking on the column heading and selecting Rename:

image

I have also changed the query name to Projects:

image

Now click Add Column > Add Custom Column:

image

Enter the name “Project Link” and the formula:

"<PWA site URL>/project%20detail%20pages/schedule.aspx?projuid=" & [ProjectId]

Update the PWA site URL to your Project Online PWA site URL and update the PDP if required, this one uses the Schedule PDP.

image

Click OK. The Projects dataset table is now ready, we now need to add in the Issues data. From within the Query Editor window, click New Source > OData Feed:

image

Enter the Issues URL and click OK:

image

Click OK on the preview window then you will see the 2nd query added:

image

Now we need to Choose Columns, remove them all and select the following: ProjectId, IssueId, ItemRelativeUrlPath, Title

Click OK. Rename the query to Issues then that dataset table is complete:

image

We now need to add in the Risks data. From within the Query Editor window, click New Source > OData Feed:

image

Enter the Risks URL and click OK, click OK on the preview window then you will see the 3rd query added:

image

Now we need to Choose Columns, remove them all and select the following: ProjectId, RiskId, ItemRelativeUrlPath, Title

Click OK. Rename the query to Risks then that dataset table is complete:

image

Now we need to merge the Issues table with the Projects table so that we can get the Project Site URL in the the Issues table. Select the Issues dataset table then click the Merge Queries option:

image

In the Merge window select the Projects table and ProjectId from both as seen below:

image

Click OK and you will see a new column appear:

image

Click the button on the new column to choose the columns to expand from the joined table:

image

Select just the Project Site URL:

image

Click OK and you will see the Project Site URL appear:

image

Rename the column to remove the NewColumn. prefix. Now click Add Column > Add Custom Column:

image

Enter a name “Issue Link” then enter the formula for the new column:

[Project Site URL] & "/" & Text.Range([ItemRelativeUrlPath],0,13) & "DispForm.aspx?ID=" & Text.Range([ItemRelativeUrlPath],13,1)

image

Click OK. Click on a row and ensure the URL is correct – copy in the browser to test:

image

Now select the Risks dataset table to repeat the steps. Click Merge Queries with the same steps as before and click OK. In the new column expand the Project Site URL then rename the column to remove the NewColumn. prefix. Add the custom column called “Risk Link” with the following formula:

[Project Site URL] & "/" & Text.Range([ItemRelativeUrlPath],0,12) & "DispForm.aspx?ID=" & Text.Range([ItemRelativeUrlPath],12,1)

image

Click OK then click on a row and ensure the URL is correct – copy in the browser to test:

image

Then click Close & Apply:

image

Then the Apply Query Changes window will load whilst the data model loads:

image

Once loaded, check the table relationships are ok and change if needed:

image

Now you are ready to build the Project links report as you would normally build a Power BI report. One additional step that you will need to do it make the URL columns into Web Urls. For example, select the “Project Site URL” from the Projects dataset then click the Modelling ribbon and under the Data Category option chose Web URL:

image

Repeat this for the three custom columns created: Issue Link, Risk Link and Project Link.

A very simple report has been created below to show the hyperlinks:

image

This is a very plain report as you can see, but this demonstrates how to create hyperlinks to keys areas of the project from a Power BI report.

#ProjectOnline Project Ideas list view with Project GUID #Office365 #SharePoint #JavaScript #jQuery

July 22, 2016 at 9:14 pm | Posted in Add-on, Administration, Configuration, Customisation, Functionality, Information, Reporting | Leave a comment
Tags: , , , , , ,

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:

image

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:

image

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:

image

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:

image

Replace ProjectIdeas with the correct title. Save the JavaScript file in a document library in the PWA site collection then create a web part page in the PWA site collection, for example I created the page and uploaded the script to the Shared Documents library:

image

On the new web page page I added a content editor web part and linked to the JavaScript file:

image

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.

#ProjectOnline Resource Engagements update #Office365 #MSProject

July 22, 2016 at 5:17 pm | Posted in Administration, Configuration, Functionality, Information | 2 Comments
Tags: , ,

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.”

https://support.office.com/en-us/article/FAQ-Resource-engagements-are-replacing-the-old-resource-plans-5ddd3242-4858-4e57-a8c1-2b20c06d959a

Next Page »

Blog at WordPress.com.
Entries and comments feeds.