#ProjectOnline #OData reporting API updated to remove #HTML tags #Office365 #BI #Excel #PowerBI

May 30, 2016 at 6:36 pm | Posted in Administration, Configuration, Customisation, Functionality, Information, Reporting | Leave a comment
Tags: , , , ,

Recently you might have noticed that the Project Online OData reporting API has been updated to remove the HTML tags, I tweeted about this last week. So before this changed the data would have look like this:

image

Notice the HTML tags such as   and </li></ul></ul></ul> in the StatusSummary field. In the PDP the data looks like this in the Status Summary multiline text field:

image

If you are still seeing HTML tags for projects these will be updated once edited and saved, After making a change to a project custom field and clicking Save on a PDP (this does a Project Summary Publish too) for this example project I then see the following in the OData feed:

image

As you can see the HTML tags are now removed from the StatusSummary field. So now in your Excel or Power BI reports you will no longer have to either use VBA in Excel to remove these or use a similar Power Query function in Excel or Power BI as detailed here.

The only down side to this change is if you use a report that can render the HTML tags to maintain the formatting set in the multiline project level custom fields on the PDP this will be lost. For example, for PS+ we use a Reporting add-in that maintains the multiline custom field formatting as seen below:

image

After the update this formatting is lost as expected making the data harder to read:

image

All is not lost though, if you want to maintain this formatting just using CSOM / JSOM or REST to get the data for the multiline project custom fields. In the example below using the REST (/_api/ProjectServer) API you can see that the HTML tags are still available:

image

Here the fields are referenced using the Internal Name rather than the Name, for example Custom_x005f_4d0daaaba6ade21193f900155d153dd4. So you will need to update any custom add-ins / reporting tools to get the multiline custom field data from these API’s if you wish to maintain the formatting.

Extract #ProjectOnline or #ProjectServer 2013 / 2016 Timesheet data #PowerShell #Office365

May 17, 2016 at 4:32 pm | Posted in Add-on, Administration, Configuration, Customisation, Functionality, Information, PowerShell, Reporting | Leave a comment
Tags: , , , , ,

This PowerShell script will use the Project Reporting OData API to extract the timesheet data between the given start and end dates. The user running the script specifies the source PWA instance URL, Username and password. They then enter the start and finish dates in yyyy-mm-dd format and run. The data will then be displayed in the console and output to a CSV file.

This script example can be downloaded here: https://gallery.technet.microsoft.com/Extract-Online-or-Server-c1cba361

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 it will prompt for the source PWA URL:

image

Then the username and password:

image

Then the start and finish dates in yyyy-mm-dd format:

image

The script will output the data to the console:

image

It will also create a CSV file in the same folder that the PowerShell script is run from:

image

The CSV file:

image

This was only run against a test PWA instance in Project Online and only my account had timesheet data for the given period, it will return all of the timesheet data for all resources for the given start and finish dates.

This example requires the user to enter the environment details when running but it could easily be updated to hard code these then the PowerShell script could be scheduled to run weekly or monthly etc. The start and finish dates could be made dynamic too.

Whilst this only reads data, as always, this script is provided as is with no warranties etc. use at your own risk and test on a test environment before using on a production environment.

#ProjectServer and #SharePoint 2010 / 2013 / 2016 May 2016 Cumulative Update #PS2010 #SP2010 #PS2013 #SP2013 #MSProject

May 10, 2016 at 9:36 pm | Posted in Administration, CU, Fixes, Functionality, Information | Leave a comment
Tags: , , , , , , , , ,

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

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

Project 2016 May 2016 update:
https://support.microsoft.com/en-gb/kb/3115105

SharePoint Server 2016 May 2016 update – Project Server 2016 fix:
https://support.microsoft.com/en-gb/kb/3115088

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

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

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

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

Project 2013 May 2016 update:
https://support.microsoft.com/en-gb/kb/3115040

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 2016 CU.

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

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

Project Server 2010 May 2016 CU Server Roll up package:
https://support.microsoft.com/en-gb/kb/3115122

Project Server 2010 May 2016 update:
< no update this month>

Project 2010 May 2016 update:
https://support.microsoft.com/en-gb/kb/3115001

SP2 is a pre-requisite for the Office 2010 May 2016 updates.

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

Introduction to #Microsoft Flow with #ProjectOnline #IFTTT #WebHooks #OfficeDev #Yammer #Office365

May 6, 2016 at 12:11 pm | Posted in Add-on, Administration, Configuration, Customisation, Functionality, Information, Workflow | Leave a comment
Tags: , , ,

At the end of April Microsoft’s Flow was made available as preview. Microsoft Flow is an If This Then That (IFTTT) service with many built in web hooks or connections to different services. You can connect to services like SharePoint Online, CRM or Twitter to name a few. A blog post from Microsoft can be found here.

In this post we will see an example of using Microsoft’s Flow service with Project Online – Microsoft’s Office 365 PPM application. When a project is created we will post a message in Yammer. Once signed in, click on My Flows from the top navigation bar:

image

From here you can view preconfigured templates or create from blank. Currently there aren’t any templates for Project Online so click create from blank. On this page you will see all of the services you can work with currently in the preview version:

image

Either start typing Project or scroll down the list to Project:

image

For this example I will choose “Project Online – When a new project is created”. You then need to sign into the Project Online PWA site:

image

Enter your credentials for the target Office 365 tenant when requested. Then enter the URL of the PWA site:

image

Now click the + button to either add an action or add a condition:

image

For this example we will just add an action without any conditions. You can add conditions in if needed though like below, if the project name contains “delivery” do something:

image

Also notice the advance mode where you can type the query condition:

image

For this demo we don’t need any conditions so I will remove that and just add an action and search Yammer:

image

Then select “Yammer – Post message” and click the sign in link then follow the steps to allow the access:

image

It’s your call to allow the access or not for services for this demo I have but only do this if you accept the terms of service. Then you can complete the details for the Yammer post:

image

This is what I have done:

image

Then give the Flow a name:

image

Click Create Flow and after a few seconds you will see the message stating this was created:

image

Click Done and the wizard is complete:

image

You can edit / delete the Flow from the My Flows page:

image

Now if I create a Project in that Project Online instance a new post will be created in the Yammer group. There maybe a minute or so delay before you see the post in the Yammer group once you create the project but here it is:

The project – “Paul Mathers test project”:

image

In Yammer, the post including the project name:

image

Notice the post if from Microsoft PowerApps.

You can check the Flow runs from the My Flow pages, click the i button at the end:

image

You will then see the following:

image

This is just a simple example – there is so much you can do even in the preview version of Flow – I’m sure more and more web hooks and functionality will be added before this is GA. Take a look today, it is very easy to use as you can see.

#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 | Leave a 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!

Getting started with #ProjectOnline development #Office365 #ProjectServer #JavaScript #PowerShell #dotNET

April 26, 2016 at 7:55 am | Posted in .Net, Add-on, Administration, App, Configuration, Customisation, Functionality, Information | Leave a comment
Tags: , ,

Just a quick post to highlight a new code sample that has been added to the Project Online code samples on GitHub found here: https://github.com/OfficeDev/O365-Project-Online-.Net-Samples

The projTool tool has been created / updated to use CSOM instead of the PSI, Brian Smith has a great walkthrough for getting started with this tool on the link below:

https://blogs.msdn.microsoft.com/brismith/2016/04/26/project-development-samples-projtoolv2/

On the GitHub samples you will find other examples for JSOM, CSOM and REST. A great place to start with Project Online development. You will also find some simple code samples / solution starters on the link below for Project Online / Project Server:

https://gallery.technet.microsoft.com/site/search?f%5B0%5D.Type=User&f%5B0%5D.Value=PWMather

#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 | Leave a comment
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!

#ProjectServer and #SharePoint 2010 / 2013 / 2016 April 2016 Cumulative Update #PS2010 #SP2010 #PS2013 #SP2013 #MSProject

April 12, 2016 at 6:39 pm | Posted in Administration, CU, Fixes, Functionality, Information | 1 Comment
Tags: , , , , , , , , ,

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

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

Project 2016 April 2016 update:
https://support.microsoft.com/en-gb/kb/3114973

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

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

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

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

Project 2013 April 2016 update:
https://support.microsoft.com/en-gb/kb/3114954

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 2016 CU.

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

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

Project Server 2010 April 2016 CU Server Roll up package:
https://support.microsoft.com/en-gb/kb/3114992

Project Server 2010 April 2016 update:
< no update this month>

Project 2010 April 2016 update:
< no update this month>

SP2 is a pre-requisite for the Office 2010 April 2016 updates.

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

#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

#Office365: quickly see which #SharePoint sites are #ProjectOnline sites #PowerShell

April 5, 2016 at 11:44 am | Posted in Administration, Configuration, Customisation, Functionality, Information, PowerShell | Leave a comment
Tags: , , ,

In Office 365 from the SharePoint admin center it is not possible to quickly see which site collections are PWA site collections. The only way currently to check in the UI is the select a site collection then click the Project Web App button on the Site Collections ribbon and see if the Remove and Settings options are enabled:

image

If you select a normal SharePoint site collection these two options are disabled:

image

As you can imagine, if you have many site collections this could be quite a slow process. There is a simple and quick answer to this, PowerShell. Using the SharePoint Online Management Shell you can access the properties of the site collections, details on the SharePoint Online Management Shell can be seen below:

https://support.office.com/en-us/article/Introduction-to-the-SharePoint-Online-Management-Shell-c16941c3-19b4-4710-8056-34c034493429

I have used the PowerShell ISE to create and run the script, to use the ISE you will need to firstly install the SharePoint Online Management Shell on your machine then import the module using the command below:

Import-Module Microsoft.Online.SharePoint.PowerShell -DisableNameChecking

Once loaded, a simple PowerShell script can easily identify the PWA site collections:

image

There is a –Filter parameter for the Get-SPOSite command but it doesn’t allow you to filter on the Template property so I created a simple foreach loop and did the filter there.

Or if you want to see all of the site collections and the templates used to create the sites see the script below:

image

In both examples just update the site collection admin site URL and the global administrator username for the Connect-SPOService command.

**** There is a caveat to this approach (thanks to Brian Smith for letting me know), if you have a normal SharePoint site then enable PWA on the site after it is created these sites will not show as a PWA site in this script. In that scenario the PWA site is a sub site and the Get-SPOSite only gets the root site collections. I guess you could look at using CSOM / REST to get all sites. ****

If would be good to get this information visible in the view from the SharePoint Admin Center, someone has already suggested this on the Office 365 uservoice, see the link below if you want to vote:

https://office365.uservoice.com/forums/273493-office-365-admin/suggestions/9374838-enable-split-view-in-sharepoint-admin-center-to-di

Next Page »

Blog at WordPress.com. | The Pool Theme.
Entries and comments feeds.

Follow

Get every new post delivered to your Inbox.

Join 1,054 other followers