Last logon time for the #ProjectOnline PWA users report #PPM #PowerBI #PowerQuery #Office365 #SharePoint #BI part 2October 12, 2016 at 4:46 pm | Posted in Add-on, Administration, Configuration, Customisation, Functionality, Information, Reporting, Workarounds | Leave a comment
Tags: Office365, Power Query, PowerBI, PPM, Project Online, SharePoint Online
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:
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:
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:
Page 2 – PWAUserLastConnectDate:
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:
The first visual we will add is the bottom left pie chart for “Logon by Browser”, from the PWAUsage dataset select Browser and Id:
It defaults to the Table visualisation, change this to the Pie chart in the Visualizations pane:
Drag Id from Details into Values:
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:
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:
By default, the Logon Date will be broken down into the date hierarchy, change this in the visualisation settings, select Logon Date:
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:
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:
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:
Change the visualisations from a table to a Stacked bar chart and move Id to Values and Browser to the Legend:
Move the visualisation to the center of the page and extend it to the right hand side of the page by dragging it:
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:
Update the visualisation settings as required by clicking the roller. I added a title and increased the size of the data text:
Add a text box to the top of the page and enter the report title, change the settings as required:
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:
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:
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:
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:
Now update the title from Total Hits to Total IE Hits:
Repeat this for the other 4 cards but set one for Chrome, Edge, Firefox and Other so you end up with this:
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:
Now repeat this but select Browser and change it to the Chiclet Slicer:
Change the settings as required, I added a title, turned off the header row and set it to have 2 columns:
That is the first page set up, rename the page and it is completed:
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:
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:
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:
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:
It supports Image URLs, for this I updated the PWAUsage dataset and added a new column called Browser URL:
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:
Then update the Chiclet Slicer settings:
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!
#ProjectServer and #SharePoint 2013 / 2016 October 2016 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProjectOctober 12, 2016 at 8:42 am | Posted in Administration, CU, Fixes, Functionality, Information | Leave a comment
Tags: Office 2013, Office 2016, Project 2013, Project 2016, Project Server 2013, PS2013
The Office 2016 October 2016 updates and cumulative updates are now available, please see the links below:
Project 2016 October 2016 update:
SharePoint Server 2016 October 2016 update – Project Server 2016 fixes:
Nothing for Project Server 2016 at the moment
The Office 2013 October 2016 updates and cumulative updates are now available, please see the links below:
Project Server 2013 October 2016 CU Server Roll up package:
Project Server 2013 October 2016 update:
Project 2013 October 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 October 2016 CU.
As always, fully test these updates on a replica test environment before deploying to production.
Last logon time for the #ProjectOnline PWA users report #PPM #PowerBI #PowerQuery #Office365 #SharePoint #BI part 1October 10, 2016 at 4:21 pm | Posted in Add-on, Administration, Configuration, Customisation, Functionality, Information, Reporting, Workarounds | 2 Comments
Tags: Office365, Power Query, PowerBI, PPM, Project Online, SharePoint Online
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:
Page 1 (PWAUsage):
Page 2 (PWAUserLastConnect):
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:
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:
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:
Also rename any columns as needed and remove the duplicate ID column, I renamed LogonDate to Logon Date and WhoString to Username:
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:
Click OK and the dataset will update:
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:
Click OK. The ResourceName column was then renamed and the Query renamed too:
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:
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:
Click OK. Update the query name to something meaningful such as PWALastLogon.
Click the Expand button next to the NewColumn:
Change the radio button to Aggregate and then click the dropdown next to Logon Date and select Maximum, don’t select anything else:
Uncheck the option “Use original column name as prefix” then click OK:
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:
Now click Close & Apply > Close & Apply from the Home ribbon menu and the report will show your queries available:
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:
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.
Tags: PPM, Project 2013, Project 2016, Project Online, Project Server 2013, Project Server 2016
A quick post to highlight an issue and workaround for opening the Enterprise Resource Pool in Project Pro using the Open button on the Resources tab in the Resource Center:
If you try and click the Open button with no resources selected in the grid you will get the error below:
“This action couldn’t be performed because Office doesn’t recognize the command it was given” :
Select at least one resource in the grid then this command will work fine.