#ProjectOnline #Project Site settings / location #SharePoint #PPM #O365 #MSProject

June 14, 2017 at 8:43 pm | Posted in Administration, Functionality, Customisation, Information, Configuration | 1 Comment
Tags: , , ,

Again, another post that is a bit later than I would normally post about changes but I’m still trying to play catch up at work and home after my vacation, I feel like I need another holiday already! Anyway, further to the announcement the other month regarding the change to support 30,000 project and 30,000 project sites in Microsoft’s Office 365 PPM tool Project Online, the final part of that change is here.

Before we jump in to the detail, a bit of history to show how the Project Product group have done a great job and massively improved the Project Online projects / project sites limit since Project Online was first released.  In the early days Project Online had a limit of 2,000 projects and 2,000 project sites. I think in the first release, both the projects and project sites were both restricted to 2,000 due to the SharePoint Online limit of 2,000 sub sites per site collection, the sub site limit is still a limit today in SharePoint Online. Details here for SharePoint Online limits: https://support.office.com/en-ie/article/SharePoint-Online-limits-and-quotas-8f34ff47-b749-408b-abc0-b605e1f6d498. The 2,000 project limit was then raised to 5,000 projects but the project site limit was still limited to 2,000 which meant that 3,000 of your 5,000 projects couldn’t have a project site. Today in Project Online you can have 30,000 projects and each of those projects can have a project site* I have put an asterisk here as there are some configuration / site collection requirements to support this as detailed in this blog post. To have 30,000 project sites you would need 15 Enterprise Project Types (EPTs) and 15 SharePoint site collections including the actual PWA site collection. This is how the Project Product group have worked around the SharePoint Online sub site limitation. Let’s look at how this is set up in PWA.

For the purpose of this blog post I have just two EPTs in my PWA site collection, the default Enterprise Project and one called Product Development. Firstly I will create a new SharePoint Online site collection via the SharePoint Admin Center in Office 365 called ProductDevSites to host the project sites in my new EPT. From the SharePoint Admin Center click New > Private Site Collection and complete the form

image

Click OK. That might take 10 to 15 minutes to provision. Once completed open the PWA site collection and navigate to the PWA Settings page:

image

Nothing different here… Clicking on the following settings will show some differences:

  • Connected SharePoint Sites
  • Manage User Sync Settings
  • Enterprise Project Type

Connected SharePoint Sites:

image

Notice the Settings button is now missing from the menu bar. The settings button here used to allow you to control if / when project sites where created. This has moved to the Enterprise Project Type page.

Manage User Sync Settings:

image

Notice there are two checkboxes missing from the Sync options. Here you could also set the Project Site Sync and the Project Site Sync for SharePoint task list projects. The setting to sync users has moved to the EPT page.

Enterprise Project Type:

image

Notice the three new sections here, Site Creation – this was on the Connected SharePoint Sites page, Site Creation Location – this a new setting and Synchronization – this contains the sync settings. Changing the Site Creation setting to either Automatically create or Allow users to choose will enable the Site Creation Location setting. This defaults to the current PWA site collection URL, for this EPT I will leave that as the location and enable the user permission sync:

image

One thing to note here regarding the synchronization options, both the user sync and the task list sync only work for project sites inside the Project Web App site collection. Save the EPT then open the other EPT/s. In this example I will edit the Product Development EPT and enable site creation but rather than creating sites in the PWA site collection I have selected to create these in the ProductDevSites site collection:

image

I could still create the Product Development project sites and other EPT’s project sites in the Project Web App site collection (PWA2 in this example) if I knew I would never exceed the 2,000 sub site limit. Notice I haven’t enabled the site sync as this would be redundant here as the site creation location is not the Project Web App site collection. Before we create some projects for each EPT, worth noting is that you might not see the same options as displayed on the EPT’s above, you might just see the following:

image

No Site Creation Location and the Sync User Permissions checkbox is disabled, this will be because your Project Web App site collection will be in the SharePoint permission mode so will be limited to up to 2,000 sub sites and the user permission sync to the project sites is not possible.

Creating a project for each EPT and publishing those projects will create the project sites. As you can see below, the project sites are in different site collections based on the EPT settings:

image

So now you can have 30,000 projects and 30,000 project sites!

Brian Smith posted about this change to other day too: https://blogs.technet.microsoft.com/projectsupport/2017/06/12/project-online-what-happened-to-my-site-creation-settings/

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

June 14, 2017 at 8:15 am | Posted in Administration, Configuration, CU, Fixes, Functionality, Information | Leave a comment
Tags: , , , , , , ,

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

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

Project 2016 June 2017 update:
https://support.microsoft.com/en-us/kb/3191934

SharePoint Server 2016 / Project Server 2016 June 2017 update: 
https://support.microsoft.com/en-us/kb/3203432 & https://support.microsoft.com/en-us/kb/3203433

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

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

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

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

Project 2013 June 2017 update:
https://support.microsoft.com/en-us/kb/3191941

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

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

Update for script to report across #ProjectOnline Project Sites for #SharePoint list data #PPM #JavaScript #Office365 #REST #OData

June 3, 2017 at 8:58 pm | Posted in Configuration, Customisation, Fixes, Functionality, Information, Reporting | Leave a comment
Tags: , , , ,

I have made a quick change to the example solution starter script to fix a common encoding issue with the EPT names. For example, if your EPT name is “R & D”, the original example solution starter script wouldn’t handle this when querying the Project OData API. It would pass in R & D when querying the OData API but the OData API call fails as it should use R %26 D. I have updated the solution starter code to handle this and encode the EPT name before querying the Project OData API. The solution starter code can be downloaded here:

https://gallery.technet.microsoft.com/Report-on-Online-list-data-f5cbf73f

If you didn’t seen the original post or solution start script before, see the post below:

https://pwmather.wordpress.com/2017/05/05/want-to-report-across-projectonline-project-sites-for-sharepoint-list-data-ppm-javascript-office365-rest-odata/

This script is still a solution starter and should be updated for production use to include the correct data you want, improve error handling, support the REST API pagination, split out HTML, CSS and JavaScript etc.

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

June 2, 2017 at 5:24 pm | Posted in Administration, Configuration, CU, Fixes, Functionality, Information | Leave a comment
Tags: , , , , , , ,

A little later than my normal posts for updates due to vacation but here are the links for the updates. The Office 2016 May 2017 updates and cumulative updates are now available, please see the links below:

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

Project 2016 May 2017 update:
https://support.microsoft.com/en-us/kb/3191870

SharePoint Server 2016 / Project Server 2016 May 2017 update: 
https://support.microsoft.com/en-us/kb/3191880 & https://support.microsoft.com/en-us/kb/3191884

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

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

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

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

Project 2013 May 2017 update:
https://support.microsoft.com/en-us/kb/3191878

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 2017 CU on 2013.

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

Want to report across #ProjectOnline Project Sites for #SharePoint list data? #PPM #JavaScript #Office365 #REST #OData

May 5, 2017 at 5:13 pm | Posted in Add-on, Administration, Configuration, Customisation, Functionality, Information, Reporting | 5 Comments
Tags: , , , ,

For those of you that are familiar with Project Server or Project Online, only the default lists and default columns from those lists are synchronised to the database reporting schema. So Project API’s like the OData API (_api/ProjectData) only have data for Risks / Issues and the default columns etc. I have published an example solution starter script that will allow data from any list on the project site to be used.

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

https://gallery.technet.microsoft.com/Report-on-Online-list-data-f5cbf73f

This solution starter should be updated before production use to include the correct data you want, improve error handling, support the REST API pagination etc. This example uses the Issues list and some example default columns from the Issues list but it can easily be updated to use a custom list on the Project Sites.

There are comments in the script to help update the script for your target Project Site list and columns. Once the script is updated, upload it to a library on the target PWA site. Create a new page on the PWA site to host the JavaScript file. Then add a content editor web part on the new page and reference the JavaScript file, for example:

image

Once added it will look like this (this in on one of my MOD demo tenants):

image

The select menu will contain a list of EPTs:

image

Changing the selection to another EPT will load a SharePoint modal pop up whilst the data loads:

image

If an EPT is selected that doesn’t contain any list items the following will be displayed:

image

There is example conditional formatting on the table:

image

The list item title is a clickable hyper link that will open the list item in a new window:

image

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

#ProjectOnline Project Center updates #O365 #PPM #PMOT #MSProject

April 20, 2017 at 7:18 pm | Posted in Administration, Configuration, Customisation, Functionality, Information, Performance | Leave a comment
Tags: , , , ,

Further to the announcement the other week regarding great improvements coming to Microsoft’s Office 365 PPM tool Project Online : https://pwmather.wordpress.com/2017/04/03/awesome-update-for-projectonline-create-and-manage-up-to-30000-projects-ppm-o365-pmot-msproject/

You may have noticed that on your Project Online PWA instance you now have two new checkbox options on the Project Center Projects ribbon to improve page load times if needed:

image

Rollups: image

Gantt Chart: image

A small change but one that will help improve page load times for users.

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

April 11, 2017 at 6:44 pm | Posted in Administration, Configuration, CU, Fixes, Functionality, Information | Leave a comment
Tags: , , , , , , ,

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

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

Project 2016 April 2017 update:
https://support.microsoft.com/en-us/kb/3178708

SharePoint Server 2016 / Project Server 2016 April 2017 update: 
https://support.microsoft.com/en-us/kb/3178721 & https://support.microsoft.com/en-us/kb/3178718

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

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

Project Server 2013 April 2017 CU Server Roll up package:
***No Server rollup package this month – install other SharePoint 2013 patches as required***

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

Project 2013 April 2017 update:
https://support.microsoft.com/en-us/kb/3178713

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 2017 CU on 2013.

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

#ProjectOnline issue with #PowerBI and the #OData URL with [] now fixed #PPM #BI #PMOT

April 11, 2017 at 11:59 am | Posted in Administration, Configuration, Customisation, Fixes, Functionality, Information, Reporting | Leave a comment
Tags: , , , ,

Just a quick post to highlight that the issue with setting the credentials for a Project Online OData connection that contained the [] for localisation is now fixed in the Power BI Service. If your OData URL contained the [] to specify the OData localisation you couldn’t set the credentials in the Power BI Service for the data refresh, you would see the error below.

For the details on the error see a previous post of mine, see the Note halfway down the post: https://pwmather.wordpress.com/2017/02/10/projectonline-ppm-powerbi-report-pack-publish-bi-reporting-powerquery-dax-office365/

It’s good to finally have this issue fixed in Power BI. The Project Online Power BI report pack I created will now refresh / work as expected in the Power BI Service: https://pwmather.wordpress.com/2017/01/03/projectonline-ppm-powerbi-report-pack-bi-reporting-powerquery-dax-office365/

Awesome update for #ProjectOnline – create and manage up to 30000 projects #PPM #O365 #PMOT #MSProject

April 3, 2017 at 8:44 pm | Posted in Administration, Configuration, Functionality, Information | 2 Comments
Tags: , , ,

A new announcement on the Office blog today detailed some changes to Microsoft Office 365 PPM tool, Project Online. It will be possible to create and manager up to 30,000 projects. This is a great news as the 5,000 limit was an issue for some organisations. What is also coming is the ability to have a project site for each project, the limit previously was 2,000 project sites. This is achieved by setting the site collection to host the project sites per EPT as the limit per site collection is 2,000 sites. Be aware though, with the new solution the user sync and task list sync is only supported for Project Sites that exist in the same site collection as the PWA site.

There are also some new options in the project center to improve the performance for page load times when you have lots of projects by turning off the data roll up and Gantt charts.

For details see the blog post here: https://blogs.office.com/2017/04/03/create-and-manage-up-to-30000-projects-in-project-online/

The Project Online software boundaries and limits article has been updated: https://support.office.com/en-us/article/Project-Online-software-boundaries-and-limits-5a09dbce-1e68-4a7b-b099-d5f1b21ba489

The article on tuning Project Online performance has also been updated with the new options: https://support.office.com/en-gb/article/Tune-Project-Online-performance-12ba0ebd-c616-42e5-b9b6-cad570e8409c

#ProjectOnline – 1 PWA site collection for all or 1 per department? #O365 #PPM #PMOT #Office365 #MSProject

March 20, 2017 at 6:55 pm | Posted in App, Configuration, Customisation, Functionality, Information, Installation | Leave a comment
Tags: , , , , ,

A question I hear a few times from organisations is “We have a new department or business unit coming on-board with Project Online, do we need a new PWA instance for them or can we use the one we already have?” The answer isn’t normally a straightforward yes or no. This post aims to cover most of the questions you need to ask when considering using the existing PWA site collection or creating a new one for a new department / business unit.

The first thing to consider is the Project Online limitations for the data such as number of projects per PWA site, check out the limits here: https://support.office.com/en-us/article/Project-Online-software-boundaries-and-limits-5a09dbce-1e68-4a7b-b099-d5f1b21ba489. Check how many projects you currently have in the PWA site collection and how many more the new business unit expect to add into the PWA site collection – if you are going to be reaching the limits on a PWA site collection then consider a dedicated PWA site collection for the new business unit. The number of PWA site collections in each Office 365 tenant will not be an issue – you can have up to 9,999. Just because you can have lots of PWA site collection doesn’t automatically mean the answer is a new PWA site collection each time!

One PWA site collection will support different PWA configurations for each business unit or department (custom fields , Enterprise Project Types etc.) by making use of the Department functionality to separate those configuration items. So for example, the R&D department only see configuration items relevant to them. So if the new business unit has different custom field / EPT requirements, that shouldn’t be a problem using a single PWA instance.

Whilst talking about configuration items, there are some items that are at the PWA site collection level that can’t be configured / tailored to each business unit or department. These would be some of the Time and Task Management options such as Time Reporting Periods, Timesheet settings and Task settings. Also some settings under the Operational Policies such as Additional Server Settings. If the new business unit has different requirements for time capturing they would need a dedicated PWA instance.

Another important aspect to consider is – will these different business units require access to the same enterprise resources to assign to tasks? Will they need to view the true resource demand / availability for these resources in one place? If this is the case then the easiest option is for the new business unit to use the same PWA site collection.

If there is a requirement to see the data from each business unit together in PWA, for example in a project center view then a single PWA site collection would be required. Similarly, if both business units projects needed to be included in the organisations portfolio strategic analysis for cost and resource requirements, a single PWA site collection will be required.

Reporting is another key factor, if the reports need to show data from all business units / departments then a single PWA instance is easier but it is still possible to generate reports that use data from multiple PWA site collections. With multiple PWA site collections this is something that can be worked around providing there was common metadata between the PWA site collections to enable projects from both PWA site collections to be viewed in the same report.

Then there is the management of the PWA site collection/s. It might be that the organisation has a central PMO function that administers the PWA site collection – adding another PWA site collection will increase their workload.

This is by no means an exhaustive list, here are just a few of the things to consider when deciding on using the existing PWA site collection or a new PWA site collection when a new business unit / department are coming on board.

Next Page »

Blog at WordPress.com.
Entries and comments feeds.