Update #ProjectOnline Resource custom field values using #PowerShell with data from #AzureAD user attributes #PPM #Offce365 #ProjectServer #CSOM

November 7, 2016 at 9:40 pm | Posted in Add-on, Administration, Configuration, Customisation, Functionality, Information, PowerShell, Reporting | Leave a comment
Tags: , , , , , , , ,

This blog post will demonstrate a simple example of how Microsoft’s PPM tool, Project Online, can include / sync metadata from Azure AD user attributes to resource custom fields in Project Online. This example script will update the resource custom field “Job Title” on my test tenant with the data from the Azure AD user “Title” attribute.

This script example can be downloaded here: https://gallery.technet.microsoft.com/Update-Online-Resource-83137b7f

The script does require some additional modules / DLLs to work. Firstly you will need the Azure AD module installed, this can be downloaded here: http://connect.microsoft.com/site1164/Downloads/DownloadDetails.aspx?DownloadID=59185. You will also need the SharePoint Online and Project Online CSOM DLLs. The DLL’s used are from the NuGet package here: https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM/16.1.5521.1200. There are later version available, check here: https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM. Download those as required. These modules can be seen here on line 3,5 and 14 in the example script, the location will need to be updated to reference the correct location for your SP / PS Online CSOM DLLs.

The user setting up the script will need to update the correct location to the DLLs required, the AD username, AD password, CSV file location, PWA instance URL, username, password and the custom field internal name. The PWA account specified will need edit access to all of the resources in PWA and the AD account will need access to read all the users in Azure AD. Ensure the variables have been updated correctly, placeholder values seen below:

image_thumb.png

In this example all users in the Azure AD will be exported, clearly if you have a large organisation it would be efficient the filter for only those users that exist in Project Online. The code matches users and resources based on the AD display name and PWA resource name when updating the resources in PWA.

To get the correct custom field internal ID I use the REST API, <PWA Site URL> + /_api/ProjectServer/CustomFields. Find the resource level custom field and copy the InternalName as seen below:

image_thumb.png

Once the PowerShell script has been updated, save it and it can then be tested on a test / non-production environment. Once executed in PowerShell, each resource found in the CSV file will be outputted as seen in the example below. In this example there are many AD users in the CSV export that do not exist in the PWA instance.

image_thumb.png

Checking in the Resource Center after the script has run you can see for the resources that exist in the CSV file created, the Job Title has been updated with the values found in Azure AD / the export CSV file:

image_thumb.png

The CSV file generated can be seen here:

image_thumb.png

This PowerShell script could be run on a schedule from a server on-prem or even in Azure / webjob. The script would just need access to save / access a CSV file and the DLLs / modules required. Fully test this script on a test / non-production PWA instance before running on a Production PWA instance.

The script is provided “As is” with no warranties etc.

Update #ProjectOnline Project custom field values using #PowerShell with data from a CSV file #PPM #ProjectServer #CSOM

November 6, 2016 at 4:44 pm | Posted in Add-on, Administration, Configuration, Customisation, Functionality, Information, PowerShell | 1 Comment
Tags: , , , , , , , ,

This blog post will demonstrate a simple example of how Microsoft’s PPM tool, Project Online, can include data from an external system. This is a very simple example using a demo CSV mock up of data that could be from an external system. The CSV part could easily be replaced by a SQL query or a REST API query to the source system etc.

Example CSV data used can be seen below:

image

As you can see, my imagination for example project names has not improved! The code uses the Project Name as the key between the two data sets – the CSV file and PWA so the names will need to match.

This script example can be downloaded here: https://gallery.technet.microsoft.com/Update-Online-Custom-Field-12f034f4

The user setting up the script will need to update the correct location to the DLLs required, the PWA instance URL, username, password, the custom field internal name and the location of the CSV file. The account specified will need edit access to all of the projects in PWA. Ensure the variables have been updated correctly, placeholder values seen below:

image

image

The DLL’s used are from the NuGet package here: https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM/16.1.5521.1200. There are later version available, check here: https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM. Download those as required.

The get the correct custom field internal ID I use the REST API, <PWA Site URL> + /_api/ProjectServer/CustomFields. Find the project level custom field and copy the InternalName as seen below:

image

Once the PowerShell script has been updated, save it and it can then be tested on a test / non-production environment. Once executed in PowerShell, each project found in the CSV file will be outputted as seen in the example below. In this example two projects exist in the CSV data but not in my example Project Online PWA instance (remember for this example, the names need to match in the CSV file and PWA):

image

Checking in the Project Center after the script has run you can see for the projects that exist in the CSV file, the project budget includes the values found in the CSV file:

image

This PowerShell script could be run on a schedule from a server on-prem or even in Azure. The script would just need access to the data to import (CSV file etc.) and the DLLs. Fully test this script on a test / non-production PWA instance before running on a Production PWA instance.

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

Last logon time for the #ProjectOnline PWA users report #PPM #PowerBI #PowerQuery #Office365 #SharePoint #BI part 2

October 12, 2016 at 4:46 pm | Posted in Add-on, Administration, Configuration, Customisation, Functionality, Information, Reporting, Workarounds | Leave a comment
Tags: , , , , ,

This is last post in this mini series for the last connect / last logon feature for Project Online, Microsoft’s PPM tool. In this post we will create the Power BI report. For those that missed the previous post see the links below, check these out first:

Firstly, capturing the last logon time: https://pwmather.wordpress.com/2016/09/30/want-to-capture-the-last-logon-time-for-the-projectonline-pwa-users-ppm-javascript-office365-sharepoint/

Secondly, part 1 of the report creation – setting up the dataset queries in preparation for this post: https://pwmather.wordpress.com/2016/10/10/last-logon-time-for-the-projectonline-pwa-users-report-ppm-powerbi-powerquery-office365-sharepoint-bi-part-1/

If you are continuing where we left off after part 1, open the saved Power BI report:

image

We have the blank canvas ready to add the data and visualisations. In the blog post we I cover creating the report below, Power BI has many options which we don’t cover here but all are intuitive so have a play!

Page 1 – PWAUsage:

image

Page 2 – PWAUserLastConnectDate:

image

Before we start, the report example I created uses a custom visual from the gallery for the Browser filter, this can be downloaded here: https://app.powerbi.com/visuals/show/ChicletSlicer1448559807354 or alternatively just use the default slicer visual like the one used for the Username filter.

Once the custom visual is imported (or choose to use the default slicer), expand the PWAUage dataset, this is the one we will use for this first page:

image

The first visual we will add is the bottom left pie chart for “Logon by Browser”, from the PWAUsage dataset select Browser and Id:

image

It defaults to the Table visualisation, change this to the Pie chart in the Visualizations pane:

image

Drag Id from Details into Values:

image

Drag the visual to the bottom left corner of the page. In the Visualizations settings pane, click the roller to access the settings, here you can change the settings as needed, for example I turned on the Legend and update the Title:

image

The next visualisation to add is the PWA Usage Details table, click anywhere on the page so no visualisations are selected then from the PWAUsage dataset select Browser, Logon Data and Username:

image

By default, the Logon Date will be broken down into the date hierarchy, change this in the visualisation settings, select Logon Date:

image

Move the visualisation to the bottom center of the page and click the Logon Date column to change the order by so the latest date is in the first row:

image

With the visualisation selected, click the roller in the visualisations settings pane to update the settings as needed. I updated the title, the grid settings, the text size for the data and changed the column order:

image

The next visualisation to add is the Hits Per User bar chart, click anywhere on the page so no visualisations are selected then from the PWAUsage dataset select Browser, Id and Username:

image

Change the visualisations from a table to a Stacked bar chart and move Id to Values and Browser to the Legend:

image

Move the visualisation to the center of the page and extend it to the right hand side of the page by dragging it:

image

The same process as before, update the visualisation settings as required by clicking the roller. I updated title, increased the size of the legend text and turned on data labels.

The next visualisation to add is the Last Refresh table, click anywhere on the page so no visualisations are selected then from the PWAUsage dataset select Last Refreshed, resize the visualisation and move it to the top right hand corner of the page:

image

Update the visualisation settings as required by clicking the roller. I added a title and increased the size of the data text:

image

Add a text box to the top of the page and enter the report title, change the settings as required:

image

The next visualisations to add are the cards showing the totals, the process is the same for all so I will only cover adding one in detail. Click anywhere on the page so no visualisations are selected then from the PWAUsage dataset select Id, change the visual from a table to a Card:

image

Move the visual to the bottom right corner of the page, resize it and update the settings as required, I added a title, removed the category label and increased the size of the data label:

image

Add 5 more cards, select the one already created then copy and paste it 5 times then place them in the correct location on the page as required:

image

The 5 additional visualisations need different settings applied as these will show the hits per Browser. To update them, select one so that the settings are visible. Drag Browser from the PWAUsage dataset to the Visual level filters setting:

image

Select IE:

image

Now update the title from Total Hits to Total IE Hits:

image

Repeat this for the other 4 cards but set one for Chrome, Edge, Firefox and Other so you end up with this:

image

The final visualisations to add to this page are the filters, with no visualisation selected, select Username from the PWAUsage dataset, change this from a table to a slicer and change the settings as required. I added a title, turned off the header row, turned of Select all and turned off single select:

image

Now repeat this but select Browser and change it to the Chiclet Slicer:

image

Change the settings as required, I added a title, turned off the header row and set it to have 2 columns:

 image

That is the first page set up, rename the page and it is completed:

image

So here you can see some useful stats around the PWA usage.

Click the + next to the first page to add a new page and rename this to PWAUserLastConnectDate:

image

Now expand the PWALastLogon dataset and select both fields, change the column order so Resource name is first then change the row order so the Resource Name is alphabetical:

image

Change the settings as needed, I added a title, turned off the horizontal grid line and increased the text size. Now add a text box to the page to add the report title:

image

On this page you can quickly see who has logged in and when plus who has never logged in since adding the JavaScript to the Project Web App homepage – unless of course they always by pass the PWA homepage or the pages where you added the JavaScript!

There are lots of options available, have a play and build great dashboards! If you used the Chiclet slicer here is a cool option to add:

image

It supports Image URLs, for this I updated the PWAUsage dataset and added a new column called Browser URL:

image

As you can see this is an if statement, based on the Browser a certain URL is set to display the correct logo for each browser, either save the images to a site you have access to or use images from the internet. Then on the report designer I set the Browser URL to be an Image URL on the Modelling tab:

image

Then update the Chiclet Slicer settings:

image

Once completed save and publish your report to Power BI or you can just use it from Power BI Desktop if needed.

Power BI offers great report visualisations, this is just a simple example, see what you can come up with!

Last logon time for the #ProjectOnline PWA users report #PPM #PowerBI #PowerQuery #Office365 #SharePoint #BI part 1

October 10, 2016 at 4:21 pm | Posted in Add-on, Administration, Configuration, Customisation, Functionality, Information, Reporting, Workarounds | 2 Comments
Tags: , , , , ,

Following on from my last post where I published an option / workaround for the last connected feature that has been removed from Project Online, this post will look at generating a Power BI report for the usage data that is captured. For those of you that missed the last post, see link below before continuing:

https://pwmather.wordpress.com/2016/09/30/want-to-capture-the-last-logon-time-for-the-projectonline-pwa-users-ppm-javascript-office365-sharepoint/

Now that we have some data captured in the list we can generate a report, for this example report I have used Power BI and Power Query but you could do something similar in Excel Power View with Power Query or even JavaScript / HTML if you really wanted to. In this post I will walkthrough all the steps needed to start creating the example report seen below:

Page 1 (PWAUsage):

image

Page 2 (PWAUserLastConnect):

image

So firstly we need to two URLs for the data used to generate this report, the first one is from the PWAUsageList, this assumes the list is called PWAUsageList, update the URL as needed:

<PWA URL>/_api/Web/Lists/GetByTitle('PWAUsageList')/Items()?$Select=WhoString,LogonDate,Browser,Id

The next one is from the Project OData Reporting API to return the active users that have an account:

<PWA URL>/_api/ProjectData/Resources()?$Filter=ResourceIsActive eq true and ResourceNTAccount ne null

Now launch Power Bi Desktop and click Get Data > OData Feed:

image

Enter the URL for the PWAUsageList as seen in the example above and click OK then click the Edit button on the preview window and the Query Editor window will open. Change the Query name from Query1 to something meaningful such as PWAUsage. Now change the LogonDate Column to Date rather than Date/TIme by right clicking on the column heading > Change Type > Date:

image

Also rename any columns as needed and remove the duplicate ID column, I renamed LogonDate to Logon Date and WhoString to Username:

image

Now we will add a custom column to this query to get the “Last Refresh” date. To do this click the “Add Column” ribbon then “Add Custom Column” and complete the details:

image 

Click OK and the dataset will update:

image

Now we need to add the Resources data source, in the query editor click Home > New Source > OData Feed and enter the Resources OData URL as seen in the example above and click OK then click OK on the data preview window. Now click Choose Columns, the only column needed is ResourceName:

image

Click OK. The ResourceName column was then renamed and the Query renamed too:

image

Now we need to create a third query table that contains data from the PWAUsage query and the ActivePWAUsers query to show the last logon time for each PWA User. We could keep just the two queries and merge the two without creating a third table but that is up to you, you would just chose the Merge Queries option if you wanted to have just two queries. For this post I will create a third dataset query. In the query editor click the Merge Queries > Merge Queries as New option:

image

ActivePWAUsers in the top table and PWAUsage is the bottom table, select Resource Name in the top section and Username in the bottom section. The default join kind is fine for this merge:

image

Click OK. Update the query name to something meaningful such as PWALastLogon.

image

Click the Expand button next to the NewColumn:

image

Change the radio button to Aggregate and then click the dropdown next to Logon Date and select Maximum, don’t select anything else:

image

Uncheck the option “Use original column name as prefix” then click OK:

image

Rename the new column to remove the “Max of” and call the column “Latest Logon Date”

We now have the three queries ready to load into the report:

image

Now click Close & Apply > Close & Apply from the Home ribbon menu and the report will show your queries available:

image

The first thing to do will be to ensure the relationships between the three datasets is correct. Click the relationships button from the left navigation and update as needed:

image

All I had to change was to join PWAUsage to ActivePWAUsers by dragging Username from PWAUsage to Resource Name in ActivePWAUsers.

Now click back to the report view and we are ready to design the report. Now we have the datasets ready, in part 2 we will look at creating and designing the report, for now ensure you save the Power BI report for later when we look at designing the report.

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 | 2 Comments
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.

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.

#ProjectOnline / #ProjectServer #Project site provisioning using #Office365 PnP remote provisioning #SharePoint #PowerShell

May 4, 2016 at 4:20 pm | Posted in .Net, Add-on, Administration, App, Configuration, Customisation, Functionality, Information, Installation | 1 Comment
Tags: , , , , , ,

For many years now Project Server deployments have used Project Sites or known as Project Workspaces before Project Server 2010. Typically most deployments have custom requirements for the sites so custom site templates were created from a site created using the default Project Site template. The updated custom site template was then linked to the Enterprise Project Type so that new projects created used the new site template. The biggest issue with this approach was that if you wanted to update the site template later on down the line all of the existing project sites would either need manually updating or writing code to traverse through all the existing sites and make the changes. With the new online world in Office 365 there are other things to think about too. If you create a new custom site template based on the default Project Site template then Microsoft roll out a new feature in the base Project Site template – your new project sites wont get that change either. This is where the PnP remote provisioning engine is great. For a while now – at least a year or 2 I think, the best practise is to stick with the default site templates Microsoft provide, so the Project Site template for example. The Enterprise Project Types should use the default Project Site template so each new project gets a site created using the default site template. But what about my custom lists, or columns or views I hear you ask – deploy the custom artefacts once the site is created from the default site template. In this post I will give you a very quick introduction to the Office 355 PnP Remote Provisioning engine which is part of the PnP core component. PnP, known as Patterns and Practices – details can be seen here: http://dev.office.com/patterns-and-practices. This will enable you to deploy your custom site artefacts.

For this example we will look at the PowerShell variant: https://github.com/OfficeDev/PnP-PowerShell but is also available with managed code. To get started with the PowerShell version follow the steps in the GitHub link to get the components installed. I have created a project / project site using the default Project Site template and added a new list called Change Requests that is linked to a Site Collection Content type in my root PWA site collection:

image

This list has two views:

image

I have also updated the default Risks list to use custom content type and included one new column:

image

I have added my new column to the All Items view:

image

This is the new site template I want to use. Typically this is where you would save as a template but not for this example.

Once the PnP components are installed on your machine, connect to the source project site using this command – update the Url for your site:

Connect-SPOnline –Url <source site URL> 

image

Enter credentials if prompted to do so.

Now use the following command to extract the site:

Get-SPOProvisioningTemplate -Out C:\Temp\PnP\NewTemplate.xml

image

This process will extract the site definition and create an XML file in the specified location:

image

At this point the XML should be modified to remove unneeded properties. For example, as this project site is linked to a project already the property bag will contain certain properties referenced to the source site – I don’t want to overwrite these settings on my target sites so I removed the property bag entries highlighted below.

image

I have also removed properties for configuration I don’t need to update, other lists etc.  See an example below, I have only left the two lists I have added / updated:

image

I don’t cover this here but I used Visual Studio – really one for the devs out there.

Once you are happy with the source XML file you are ready to deploy this to the existing project site/s. In this example I have a test project site created by the default Project Site template that has not been modified:

image

In PowerShell I now connect to the test target site using the command below – update the Url for your site:

Connect-SPOnline –Url <target site URL> 

image

Then run the following command to apply the changes:

Apply-SPOProvisioningTemplate -Path C:\Temp\PnP\NewTemplate.xml

image

Once completed the test target site should be updated, in this example, with a new list and updated risk list. Once you are happy with the test target project site you could repeat the process on other project sites. I have found some settings are not set correctly and some do generate errors in PowerShell but there are usually monthly updates the PnP code so always ensure you regularly update the modules using the Update-Module command.

This is a very simple example using PowerShell, in production you might have a full script that has a list of Project Sites you want to update and get the script to update them all etc. Or better still, go down the manage code route and create an event driven SharePoint provider hosted add-in to do it. Either way, fully test this process on test project sites / projects first before any production projects / project sites!

#Office365 #Project Portfolio Dashboard add-in for #ProjectOnline #ProjectServer #BI #PPM

April 22, 2016 at 4:33 pm | Posted in Add-on, Administration, App, Customisation, Functionality, Information, Reporting | 2 Comments
Tags: , , , ,

In this post we will look at the recently released Office 365 Project Portfolio Dashboard for Project Online / Project Server 2013 / 2016, see the announcement below:

https://blogs.office.com/2016/04/19/new-office-365-project-portfolio-dashboard-apps-are-live/

A directly link the the SharePoint add-in can be found here: https://store.office.com/en-us/WA104380116.aspx

I have loaded this on to one of our demo instances to take a look:

image

The add-in is accessed from the PWA site contents menu:

image

Worth noting is that the users will need to be a member of one of the following SharePoint groups for the Portfolio Dashboard to work when in the SharePoint permission mode:

Administrators for Project Web App
Portfolio Managers for Project Web App
Portfolio Viewers for Project Web App

When in the Project permission mode the users will need access to “Access Project Server Reporting Service” permission and be added to one of the SharePoint permission groups above.

When the add-in is first loaded it will load the data and cache it – it will tell you it is doing this. Then in the top right corner it will display the details for when the data in that dashboard was last updated / loaded:

image

You can then refresh the data as required and it will update to indicate the refresh has started:

image

Depending on the amount of data this might take some time.

The default dashboard is “This year’s projects”, there are 6 dashboards included by default, these are available in the Dashboard tab on the ribbon:

image

Each show different data. Each dashboard has different sections or pages, for example on This Year’s Projects I can view Projects:

image

Or Tasks:

image

Or Resources:

image

Or Content:

image

Some of the tables in the views have multiple views or sheets, for example the Resources shows Work by default but can view Issues, Risks or Availability:

image

In most pages you can either drill down or click though, for example from the Overview page on the table at the bottom I can click the project name to drill down to more detail for that project:

From:

image

To:

image

Clicking the task name will load the schedule PDP in a different tab.Clicking a risk or issue will load the list item in a different tab.

Notice the left navigation updates to show you where you are with more options. For example I can go from the project dashboard view to an Executive view:

image

I can then go back to the overall dashboard view by using the navigation section.

For each dashboard you can filter the data using the Filter tab:

image

The options tab will give you the ability to change the settings for the dashboard:

image

On the Dashboard tab you also have the ability to create your own dashboard using the create button, that will display a new tab on the ribbon:

image

Firstly give it a name and description.

image

Then select the projects to include:

image

Depending on the field type you will get different options to select, for example selecting a date field will give you this:

image

Then chose the layout for each section and the components on each:

image

Update each section as required then set any filters you want available:

image

Once completed click OK and the new dashboard will be available on the Dashboard menu for all users:

image

Download it today and take a look!

#ProjectOnline Project Detail Pages issue with new look document libraries #SharePoint #O365

April 7, 2016 at 6:58 pm | Posted in Administration, Configuration, Customisation, Fixes, Functionality, Information | 1 Comment
Tags: , ,

Recently you may have noticed the banner below on a document library in SharePoint / Project Online stating “Document Libraries are getting a new look!” with a link to check it out:

image

After clicking this link, the document libraries look like this:

image

You can change to different views such as the grid view:

image

image

You can easily change the columns displayed using the ellipsis on the right hand side:

image

Create new documents:

image

All looks good… but how do I create a new Project Detail Page now? Well there are two options (there may be others too):

1: Click the “Return to classic SharePoint” link in the bottom left corner then create the PDP’s as normal

image

Or:

2: Edit the library settings by clicking the settings cog > library settings:

image

Click Advanced Settings and Allow management of content types:

image

Click OK and you will see the “Project Detail Page” content type:

image

Now go back to the library and you will see the New menu now shows the Project Detail Pages:

image

Next Page »

Blog at WordPress.com.
Entries and comments feeds.