#ProjectServer and #SharePoint 2013 / 2016 August 2017 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject
August 10, 2017 at 7:46 am | Posted in Administration, CU, Fixes, Functionality, Information, Installation | Leave a commentTags: Office 2013, Office 2016, Project 2013, Project 2016, Project Server 2013, Project Server 2016, PS2013, PS2016
The Office 2016 August 2017 updates and cumulative updates are now available, please see the links below:
https://support.microsoft.com/en-us/kb/4036121
Project 2016 August 2017 update:
https://support.microsoft.com/en-us/kb/4011034
SharePoint Server 2016 / Project Server 2016 August 2017 update:
https://support.microsoft.com/en-us/kb/4011049 & https://support.microsoft.com/en-us/kb/4011053
The Office 2013 August 2017 updates and cumulative updates are now available, please see the links below:
https://support.microsoft.com/en-us/kb/4036121
Project Server 2013 August 2017 CU Server Roll up package:
https://support.microsoft.com/en-us/kb/4011074
Project Server 2013 August 2017 update:
https://support.microsoft.com/en-us/kb/4011082
Project 2013 August 2017 update:
https://support.microsoft.com/en-us/kb/4011084
Also worth noting, if you haven’t done so already, install Service Pack 1 http://support2.microsoft.com/kb/2880556 first if installing the August 2017 CU for 2013.
As always, fully test these updates on a replica test environment before deploying to production.
Running #ProjectOnline #PowerShell in #Azure using #AzureFunctions #PPM #Cloud #Flow #LogicApp Part2
August 1, 2017 at 4:32 pm | Posted in Add-on, Administration, Configuration, Customisation, Functionality, Information, PowerShell, Workflow | Leave a commentTags: Azure Function, Flow, Logic App, Office365, PowerShell, PPM, Project 2016, Project Online
Following on from part 1 where I introduced the idea of automating certain Microsoft 365 PPM Project Online customisations using PowerShell, Microsoft Flow / Azure Logic Apps and Azure Functions, in part 2 I will set up an example automation for creating a Project Online event driven snapshot application on project published without having to set up any server or write any complied code! If you missed part 1 where this concept was introduced, see the link below:
Firstly I created an Azure Function app in my Azure subscription then created a new function based on the HttpTrigger – PowerShell template:
Give the function a name and set the Authorisation level – set the authorisation level to the correct setting for your function. Click Create. For details on Azure Functions, start here: https://docs.microsoft.com/en-us/azure/azure-functions/
You will then be presented with the function and sample code:
We will now create the PowerShell script to create the snapshot. This is based on a script I published a while back: https://pwmather.wordpress.com/2016/08/26/projectonline-data-capture-snapshot-capability-with-powershell-sharepoint-office365-ppm-bi/
The script has been updated to work in an Azure Function but also modified to use a parameter so that it only captures data for the published project, the PowerShell script can be seen further on in the post.
Firstly upload the SharePoint CSOM DLLs using the upload button:
I used the SharePoint CSOM DLLs from the SharePoint Online Management Shell:
Then enter the PowerShell code – screen shots below and code pasted below the images:
Code sample used in function:
# POST method: $req
$requestBody = Get-Content $req -Raw | ConvertFrom-Json
$projID = $requestBody.projID
# GET method: each querystring parameter is its own variable
if ($req_query_name)
{
$projID = $req_query_name
}
#add SharePoint Online DLL - update the location if required
Import-Module "D:\home\site\wwwroot\ProjectSiteUserSyncHTTPTrigger\Microsoft.SharePoint.Client.dll"
Import-Module "D:\home\site\wwwroot\ProjectSiteUserSyncHTTPTrigger\Microsoft.SharePoint.Client.Runtime.dll"
#set the environment details
$PWAInstanceURL = "https://mod497254.sharepoint.com/sites/PWA2"
$username = "admin@MOD497254.onmicrosoft.com"
$password = "password"
$securePass = ConvertTo-SecureString $password -AsPlainText -Force
#create the SharePoint list on the PWA site and add the correct columns based on the data required
$listname = "ProjectSnapShots"
$results1 = @()
#set the Odata URL with the correct project fields needed
$url = $PWAInstanceURL + "/_api/ProjectData/Projects()?`$Filter=ProjectId eq GUID'$projID'&`$Select=ProjectId,ProjectName,ProjectPercentCompleted"
#get all of the data from the OData URL
while ($url){
[Microsoft.SharePoint.Client.SharePointOnlineCredentials]$spocreds = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($username, $securePass);
$webrequest = [System.Net.WebRequest]::Create($url)
$webrequest.Credentials = $spocreds
$webrequest.Accept = "application/json;odata=verbose"
$webrequest.Headers.Add("X-FORMS_BASED_AUTH_ACCEPTED", "f")
$response = $webrequest.GetResponse()
$reader = New-Object System.IO.StreamReader $response.GetResponseStream()
$data = $reader.ReadToEnd()
$results = ConvertFrom-Json -InputObject $data
$results1 += $results.d.results
if ($results.d.__next){
$url=$results.d.__next.ToString()
}
else {
$url=$null
}
}
#add data to snapshot list
#get PWA site client context
$ctx = New-Object Microsoft.SharePoint.Client.ClientContext($PWAInstanceURL)
$credentials = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($username, $securePass)
$ctx.Credentials = $credentials
$ctx.ExecuteQuery()
#get the target list
$List = $ctx.Web.Lists.GetByTitle($listname)
$ctx.Load($List)
$ctx.ExecuteQuery()
#for each project, create the list item - update the newitem with the correct list columns and project data
foreach ($projectrow in $results1)
{
$itemcreationInfo = New-Object Microsoft.SharePoint.Client.ListItemCreationInformation
$newitem = $List.AddItem($itemcreationInfo)
$newitem["Title"] = $projectrow.ProjectName
$newitem["ProjectId"] = $projectrow.ProjectId
$newitem["PercentCompleted"] = $projectrow.ProjectPercentCompleted
$newitem.Update()
$ctx.ExecuteQuery()
}
The PowerShell code would need to be updated with your environment details: (PWAInstanceUrl, username, password and listname variables). Also the OData URL will need to be updated to include the project level fields that you want to snapshot.The target SharePoint list will also need to be set up in the PWA site collection for the project fields the script uses. This is the list I set up for this example:
SnapshotDate is set to Todays date so we don’t need to set that in the code.
The code is simple to follow but in summary the first part will get the projID from request body – we will pass in the ProjectID for the published project from the Flow / Logic App trigger. Then the SharePoint Online CSOM DLLs are imported in. Then the specific PWA environment details are set for the variables. The OData URL is then added to the url variable. Here notice we are filtering for the ProjectID and passing in the $projID variable we get from the request body. The Select part of the query will need to be updated for your project level fields. Next the code gets the data from the OData feed using the web request and adds the data into the results array. Once we have the data, we connect to the SharePoint list, in the example it is the ProjectSnapShots as set in the $listname variable. Lastly the new item is created in the list using the data from the results array.
Now the Azure Function is ready to be used. It can be tested using the Test option in the right hand panel, update the Request body:
Update it for a valid project ID. Then click Run above the function code:
The Logs window below will help you debug any errors etc.:
Then check the SharePoint list in the PWA site and the new item should have been created:
We now know the Azure Function is working as expected, now we need to call the Azure function when a project is published. All we need from the Azure Function is the URL to use, use the </>Get function URL button:
Select the correct Key, in this example I used the default function key. Copy the URL as it will be needed later.
To call the Azure Function when a project is published, the choice here for a no code option would be Microsoft Flow or Azure Logic App. For this I will use Microsoft Flow but the same steps (triggers , actions etc.) would be used in the Azure Logic App. Create a new Flow and search for Project Online:
Then select the Project Online – When a project is published trigger.
Enter the PWA URL:
Then click the ellipsis and set the connection for the PWA URL or create a new connection if needed:
Click + New step then Add an Action and search Http:
Select HTTP – HTTP:
Complete the HTTP action:
Method is POST, the Uri is the URL for the function that we copied earlier, Headers are not required. The Body is where we pass in the project ID from the published project trigger:
The Flow is now completed:
Now click Save flow.
In PWA, Publish a project or projects and see the snapshot data created on the configured snapshot list once the Flow has run:
Flow run:
Data added to the list for the project I published – in this example it was the Office 2016 rollout project:
This just shows a simple example and the some of the possibilities for extending the Project Online capability when making use of simple PowerShell scripts and other Microsoft 365 / Azure services for cloud / serverless solutions. Look out for more examples in the future.
Running #ProjectOnline #PowerShell in #Azure using #AzureFunctions #PPM #Cloud #Flow #LogicApp Part1
July 28, 2017 at 4:50 pm | Posted in Add-on, Administration, App, Configuration, Customisation, Fixes, Functionality, Information, PowerShell, Workflow | 4 CommentsTags: Azure Function, Flow, Office365, PowerShell, PPM, Project 2016, Project Online
Following on from my last post where I published an example solution starter PowerShell script for adding project team users to the Project Site, here I mentioned about running the script in an Azure Function and even running this sync from a Project Online event. The blog post can be seen below if you missed that:
Whilst I will use that example PowerShell script from my last blog post as an example, the concept will work for any PowerShell script.
I wont cover the details in setting up the Azure Function in part 1 as there is plenty of support out there for this – for this example I created an Http Trigger – PowerShell function.
I then uploaded the SharePoint DLLs and copied in the PowerShell script into the editor:
The project site user sync script didn’t work as is as I had to make some minor changes to get this to run from the Azure Function. This included change the way the SharePoint CSOM DLLs where loaded in. In the example script I used Add-Type to load the DLLs but in the Azure Function I had to switch this out to use Import-Module:
The next change I had to make was to comment out all of the feedback to the console, so all of the write-hosts. I also had to remove the functions within the script so that is was one block. After these changes I could execute the PowerShell script to add the project team members from my example project into the associated project site from the Azure Function. As this was an HTTP Trigger Azure Function, you can get the URL to the function and access that URL to execute the function.
This opens up lots of possibilities to easily execute this Azure Function from other applications that can make the HTTP call. For example you build easily execute this script once the project has been published either using a remote event receiver (RER) or a Microsoft Flow / Azure Logic App. The example script would need to be made generic and pass in a variable into the Azure Function for it to be a workable solution.
In part 2 of this blog post we will look at make a full event driven solution that is fired on project publish then executing the Azure Function and passing in a variable.
#ProjectServer and #SharePoint 2013 / 2016 July 2017 Cumulative Update #PS2013 #SP2013 #PS2016 #SP2016 #MSProject
July 16, 2017 at 2:25 pm | Posted in Administration, CU, Fixes, Functionality, Information | Leave a commentTags: Office 2013, Office 2016, Project 2013, Project 2016, Project Server 2013, Project Server 2016, PS2013, PS2016
The Office 2016 July 2017 updates and cumulative updates are now available, please see the links below:
https://support.microsoft.com/en-us/kb/4033107
Project 2016 July 2017 update:
https://support.microsoft.com/en-us/kb/3203476
SharePoint Server 2016 / Project Server 2016 July 2017 update:
https://support.microsoft.com/en-us/kb/3213544 & https://support.microsoft.com/en-us/kb/3213543
The Office 2013 July 2017 updates and cumulative updates are now available, please see the links below:
https://support.microsoft.com/en-us/kb/4033107
Project Server 2013 July 2017 CU Server Roll up package:
https://support.microsoft.com/en-us/kb/3213566
Project Server 2013 July 2017 update:
https://support.microsoft.com/en-us/kb/3213577
Project 2013 July 2017 update:
https://support.microsoft.com/en-us/kb/3213538
Also worth noting, if you haven’t done so already, install Service Pack 1 http://support2.microsoft.com/kb/2880556 first if installing the July 2017 CU for 2013.
As always, fully test these updates on a replica test environment before deploying to production.
#ProjectOnline & #ProjectServer #PS2013 / #PS2016 Global Permissions access to PWA Settings Cog #SharePoint menu items
July 13, 2017 at 8:44 pm | Posted in Administration, Configuration, Customisation, Functionality, Information | Leave a commentTags: Office365, PPM, Project 2013, Project 2016, Project Online, Project Server 2013, Project Server 2016
I wrote the same blog post but for Project Server 2010 over 5 years ago: https://pwmather.wordpress.com/2012/05/31/projectserver-2010-global-permissions-access-to-pwa-site-actions-menu-items-ps2010-sp2010-msproject/ This blog post will cover the same but for Project Online / Project Server 2013 / 2016. This is useful for PWA site collections that are using the Project Permission mode as you can add / remove these permissions as required. Below I have listed the Project Server /Project Online global permissions and the Settings Cog SharePoint menu items that are available when the permissions are allowed.
- Log On
- Allows access to the following Site Actions menu items:
- Site contents
- Log On + Manage Lists in Project Web App
- Allows access to the following Site Actions menu items:
- Edit page
- Add an app
- Site contents
- Change the look
- Site Settings (limited options)
- Log on + Manage Lists in Project Web App + Manage SharePoint Foundation
- Allows access to the following Site Actions menu items:
- Edit page
- Add an app
- Site contents
- Change the look
- Site Settings (all options except Site Collection Admin (SCA) options)
#ProjectOnline project user sync to project sites #PPM #O365 #PowerShell #SharePoint
July 7, 2017 at 4:13 pm | Posted in Add-on, Administration, App, Customisation, Functionality, Information, PowerShell, Workarounds | 1 CommentTags: Office365, PowerShell, PPM, Project 2016, Project Online
This is a supporting blog post for an example solution starter PowerShell script I wrote for Microsoft’s Office 365 PPM tool Project Online. With the great improvement from Microsoft to now support up to 30,000 Projects and Project Sites in one Project Online Project Web App site collection, there are some limitations such as not being able to sync the users to project sites outside of the PWA site collection. For details on this change see the post here:
This solution starter script just demonstrates one method to sync the project team members into the associated Project Site- the concept would also be useful when using the SharePoint permission mode in PWA. The example script is fixed to one example project / project site and only adds the team members to the members SharePoint group on that site. It doesn’t loop through all projects or remove users from the project sites etc. This could all easily be done but is beyond the scope of the code sample / solution starter.
The code sample / solution starter can be downloaded from here: https://gallery.technet.microsoft.com/Online-User-Sync-to-7a75ef77
To get the script to work, there will need to be some environment variables set and a DLL available, these are detailed below.
To get the script to work you will need to reference the DLL as seen in the image below:
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.
You will then need to update the environment detail placeholders as seen below:
Add the Full PWA URL, username and password for an account that is a full admin on the PWA site collection. Select an example project to test with on a non-production PWA project / project site. Use a project that is not syncing the users to the project site automatically – for example a project site outside of the PWA site collection. Copy the Project GUID – it will be similar to this: 4b75dfb8-4051-e711-80c9-00155da85037 and update the script with the project GUID. An easy way to get the Project GUID is from the PWA PDP URL when accessing the project. For the same project, copy the full project site URL and update the script then find the name of the correct SharePoint group to add the users to. For example it could be the members group. The groups can be found from the project site > Settings cog > Site Settings > Site Permissions.
Once these variable placeholders are set, save the script. Run the script using PowerShell and you will see the users added to the specified group on the project site. Fully test this on a non-production PWA instance first. The code should really be updated to production standard code before using on a production PWA instance and handle removing users, adding users to different permissions groups based on role and dynamically getting the projects and project site urls etc.
Below you can see the output from the PowerShell ISE when running against my example project / project site on my test PWA instance:
Looking at the project site you can see the users here:
A production version of the PowerShell script could be set to run each day / night etc. as required. The code could also easily be run using an Azure Function and executed from a URL – you could then build is an event driven type user sync – more on that in my next blog post.
The script is provided "As is" with no warranties etc. – this is just a free solution starter so is use at your own risk.
#Project #MVP Award #ProjectOnline #ProjectServer #MVPBuzz #Microsoft
July 3, 2017 at 12:35 pm | Posted in Information, Personal | 3 CommentsTags: MVP
I had some great news over the weekend – I was renewed as a Business Solutions – Project MVP for 2017 – 2018. This is the 5th consecutive year after first being awarded in April 2013. I am really grateful for the recognition, especially as I still enjoy helping out the Project and Project Server / Project Online community so much.
#ProjectOnline Reporting #OData entity modified dates #PPM #PMOT #O365
July 1, 2017 at 7:21 pm | Posted in Administration, Configuration, Functionality, Information, Reporting | Leave a commentTags: Office365, PPM, Project Online
Just a quick blog post to highlight a feature in the OData reporting API so that you are aware of how it works. A few months back it was announced that all entities in the OData API would have modified dates. I thought this would be a great addition as those that pulled the data into a SQL database could then just pull down the deltas to minimise the data from Project Online into the database. I for one hadn’t really looking into the new modified date properties as I just assumed they would be true modified dates when those entities where updated. So for example, I thought if I just opened and published a project without changing any task data only the Project Modified Date would change and the Task Modified Dates would remain as the previous dates when those tasks were actually modified. This assumption was incorrect, in that scenario where you only open then publish the project without making changes to any tasks, all task modified dates are also updated to match the project modified date. See the example below:
The Office 2016 rollout plan on my test Project Online system was created over a month ago as were all of the example tasks. Today I just opened the project and published it without making any changes to any tasks but notice the ProjectModifiedDate and TaskModifiedDates all match:
Checking the Task Time phased task modified dates shows the same thing:
If I just add a new task then publish the project the same happens, the project modified date is updated as expected but also all tasks are updated to have the same task modified date as the project modified date:
I have also seen examples where adding one new task doesn’t impact the modified dates of other tasks.
If I now left that project open for a couple of minutes without making any changes then hit publish again, this time I do see only the Project Modified Date change as expected, in that scenario the task modified dates remain the same.
Here are examples for task data and task time phased data but the same occurs in all feeds such as assignment time phased, assignment baseline time phased etc.
Just something to be aware of if you were wondering why the dates were always being updated – may be you had the same assumption as I did! If you are using the entity modified dates, make sure you test all scenarios to ensure you know when dates do and don’t get updated.
I have put an idea on the user voice forum – if you agree it would be good to change these dates to true modified dates – get voting 
https://microsoftproject.uservoice.com/forums/218133-microsoft-project/suggestions/19821661-have-true-entity-modified-dates-in-the-odata-api-f
#ProjectOnline #Project Site settings / location #SharePoint #PPM #O365 #MSProject
June 14, 2017 at 8:43 pm | Posted in Administration, Configuration, Customisation, Functionality, Information | 2 CommentsTags: Office365, PPM, Project 2016, Project Online
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
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:
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:
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:
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:
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:
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:
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:
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:
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 commentTags: Office 2013, Office 2016, Project 2013, Project 2016, Project Server 2013, Project Server 2016, PS2013, PS2016
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.
Author Details
-
Create a free website or blog at WordPress.com.
Entries and comments feeds.
