Archive

Author Archive

#ProjectOnline CSOM DLL now available in #SharePoint NuGet package

February 5, 2016 Leave a comment
Paul Mather
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011.
I am also a certified Prince2 Practitioner.

This article has been cross posted from pwmather.wordpress.com (original article)

Quick post to highlight that the Project Online CSOM DLL ‘Microsoft.ProjectServer.Client.dll’ is now available via the NuGet package for SharePoint, see the blog post below for details:

http://bit.ly/1PWBtCA

Direct link to the package: http://bit.ly/1SO8x4X

Categories: Paul Mather, Work Tags:

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

January 12, 2016 Leave a comment
Paul Mather
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011.
I am also a certified Prince2 Practitioner.

This article has been cross posted from pwmather.wordpress.com (original article)

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

http://bit.ly/1KbV7sH

Project 2016 January 2016 update:
http://bit.ly/1JIOjrw

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

http://bit.ly/1KbV7sH

Project Server 2013 January 2016 CU Server Roll up package:
http://bit.ly/1KbV685

Project Server 2013 January 2016 update:
http://bit.ly/1JIOjry

Project 2013 January 2016 update:
http://bit.ly/1KbV7IW

Also worth noting, if you haven’t done so already, install Service Pack 1 http://bit.ly/1uorn2C first if installing the January 2016 CU.

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

http://bit.ly/1KbV7sH

Project Server 2010 January 2016 CU Server Roll up package:
http://bit.ly/1KbV7IY

Project Server 2010 January 2016 update:
http://bit.ly/1JIOjHO

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

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

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

Categories: Paul Mather, Work Tags:

Want to query cross #project site #SharePoint lists in #ProjectOnline / #ProjectServer ? #PowerBI #PowerQuery #BI #Office365 #Excel #PPM

January 5, 2016 Leave a comment
Paul Mather
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011.
I am also a certified Prince2 Practitioner.

This article has been cross posted from pwmather.wordpress.com (original article)

As you may know or not know, creating a report that contains data from a custom SharePoint list from all Project sites, for example a Lesson Learned list or Change list is not that simple. The default lists for Issues and Risks are simple as the data is synchronised to the reporting schema and available in the Project OData reporting API. In this blog post I will show you a simple example using Power Query to access the list data and create a simple cross project report consuming data from the SharePoint list APIs on the Project Sites.

In this example I use the Issues list but the same principle will apply to any SharePoint lists on the project sites. I have used Power BI Desktop to author this report but the same would work in Excel using Power Query. First load Power BI Desktop and click Get Data >  ODATA Feed and enter the REST API for the list using an example Project Site:

image

The URL I used was: https://TenantURL/sites/PSP/Acquisition%20Target%20Analysis/_api/web/lists/GetByTitle(‘Issues&#8217;)/Items()?$Select=Title,Priority

In this example I am only getting the item title and priority from the Issues list. To use a different list update GetByTitle(‘Issues’) with the name of your list and then update the Select to include the correct columns.

Click OK and you will see the data from this list:

image

Click Edit to load the query editor.

image

Rename the query to something meaningful;

image

Access the Advanced Editor:

image

Change the Power Query code to add in the following code to turn this into a parameterised function:

image

The top and bottom lines were added and the OData.Feed URL updated the remove the reference to the example site we used to load the initial data, this was replaced with the site parameter. Click Done and you will see the following:

image

Don’t invoke the function as this will edit the code. Now we need to add in the query to get the list of projects. So within the query editor on the Home tab click New Source > ODATA Feed and enter the URL to get you list of Projects and Project Site URLS:

image

The URL I used was: https://TenantURL/sites/PSP/_api/ProjectData/Projects()?$Filter=ProjectType ne 7

This filters out the Timesheet row, the properties will be selected in the next step. Click OK to load the data:

image

Click OK and click Choose Columns:

image

I only selected ProjectName and ProjectWorkspaceInternalUrl, other columns can be added but only these were required for this example:

image

Click OK and rename the Query to something meaningful:

image

We now need to add in a custom column to call the function. Click Add Column > Add Custom Column and enter the following:

image

So above we are calling the LoadIssueData function and passing in the ProjectWorkspaceInternalUrl. This will be used in the site parameter value. Click OK and the data will load:

image

The column needs to be expanded to show the data, click the expand button next to the column name and chose the columns to expand:

image

Click OK to load the data and expand the columns to see Title and Priority columns from the Issues list:

image

Now click Close & Apply from the Home tab to load the data model:

image

We can now create a report that displays the data, a simple table example can be seen below:

image

The expanded column can be renamed to something more meaningful, for example:

image

Depending on the number of projects / project sites the data load might take a while as it has to traverse all of the project sites and get the SharePoint data using the list REST APIs. Each Project requires a separate REST call to get the list data from the associated Project Site.

Hopefully that will open up your reporting options for getting data from those custom SharePoint lists or the Project sites or even if you want to use the default Issues and Risks list but have custom columns on those lists.

Categories: Paul Mather, Work Tags:

#ProjectOnline auto generated unique #Project ID #Office365 #MSProject #PMO #PMOT

December 31, 2015 Leave a comment
Paul Mather
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011.
I am also a certified Prince2 Practitioner.

This article has been cross posted from pwmather.wordpress.com (original article)

Following on from the announcement a while back and the details on the Office 365 roadmap, you might see the unique Project ID feature now available on your tenant. The link to the roadmap notification is below:

http://bit.ly/1LN3zPA

This feature enables you to create a unique Project ID for each project in a particular Enterprise Project Type (EPT). To access the configuration for the unique ID click PWA Settings > Enterprise Project Types and click on the EPT that you require a unique ID for each project. This is an EPT setting and not a global setting. Once navigated to the EPT page you will see the following section – Project Id:

image

The starting number and minimum digit padding settings are required but you can also set a prefix and post fix. On my demo environment I set the following:

image

This feature adds a new default Project ID field as seen on my PDP:

image

This field is also added to all the default Project Center views such as the Summary view as seen below:

image

It can be added to new Project Center views too:

image

The project id is set when the project is created using that EPT, so for existing projects a Project ID will not be set even if you edit it and publish it. The “Pauls Test Project 001” existed before the feature was available on my PWA instance, as you can see this has a blank Project ID field:

image

You can type an ID in there if needed, for example I manually typed the next number available (00003):

image

I then created another new project but this duplicated the Project ID as seen below for project “Pauls Test Project 4”:

image

You can also modify a Project ID that was auto generated, see project “Pauls Test Project number 002” below:

image

This new field is available in the Odata Reporting API (_api/ProjectData/Projects), it is called ProjectIdentifier as seen below:

image

It is also available in the JSOM REST API (_api/ProjectServer/Projects) as well:

image

This is a great new addition to Project Online, just be aware that existing Projects wont get an ID generated and the Project ID can be set / updated manually.

Categories: Paul Mather, Work Tags:

Update multiple #ProjectOnline PWA Instances using c# .Net console app #Office365 #csharpe #PPM #PMOT

December 23, 2015 Leave a comment
Paul Mather
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011.
I am also a certified Prince2 Practitioner.

This article has been cross posted from pwmather.wordpress.com (original article)

Following on from a post I wrote over a month ago regarding checking entities from multiple Project Online PWA instances, this post covers updating multiple Project Online PWA instances. The first post can be found below:

http://bit.ly/1GMeEUi

In this post I demonstrate a way in which you can manage configuration across multiple PWA instances, for example you might want to create a new custom field on more than one instance. This is a simple example just to show you the idea. As this is very much an example, I haven’t released any code or solution but you can see the core code further on in the post.

For the purpose of this blog post I created a C# .Net console application. Once you have a new visual studio console app project you will need to add the references to the following DLLs:

image

I used the v15 SharePoint and Project Server dlls here.

In the program add these dlls:

image

The first part of the code is to capture the custom field name and description plus the number of PWA instances to update:

image

It then goes into a loop to create the custom field on the specified PWA site:

image

The code below is used to secure the password in the console input:

image

That is it. This example will create a Project level custom field but you could easily update the code to get the user to enter the entity type (task / resource etc.)

To see this in action see below:

Enter the custom field name:

image

Enter the custom field description:

image

Enter the number of PWA instances to update:

image

Enter the first PWA site URL:

image

Enter the username for an account that has access to create custom fields:

image

Enter the password for that account:

image

After pressing enter it will go off and create the custom field on the first PWA instance:

image

Press any key and it will go back to ask for the 2nd PWA instance:

image

It will then prompt for the username and password as before. It will keep looping through depending on how many PWA sites needed to be updated.

On one of those PWA instances we can see the field was created:

image

Nice and easy, saves navigating around multiple PWA site collections for a simple change you might want to roll out across multiple instances.

Categories: Paul Mather, Work Tags:

#SharePoint or #ProjectServer 2016 Installation – Step By Step

December 19, 2015 Leave a comment
SharePoint/ProjectServer 2016 Beta 2 version is available to explore now, and in this blog post I will walk through installation steps to help users follow and setup an on-premises SharePoint server 2016 farm.

Note that Project Server service application is now included within a same set of setup files. We don’t have to install separate setup files for Project Server, you will find Project Server Service application to choose to configure as part of farm configuration step.

During the installation process, I will highlight any new/additional steps or installation screens specific to SharePoint 2016. Also note that this installation is carried using Beta 2 version, that is 99% feature complete as Microsoft has quoted and must be very identical to the RTM version coming next year.
Hardware and Software requirement for SharPoint Server 2016 can be found here: http://bit.ly/1PcxZhL
For testing purposes, I am preparing a single server farm and I have a separate database server that is running SQL Server 2016 CTP 3.0.

Exactly like SharePoint 2013, lets start with installation of prerequisites. 

Pre-requisites options: 

SharePoint server expects certain pre-requisites to be installed prior to actual SharePoint installation. Below are our option to prepare SharePoint server with pre-requisites:
  1. Online installation, using Pre-requisite tool (recommended)
  2. Manual installation of pre-requisites by downloading required setups files.

For offline installation (option-2), you can download below required pre- requisites and install on server. Please always refer to this MSDNto check for any changes in pre-requisites and their respective download links:
·        Web Server (IIS) role
·        Application Server role
·        Microsoft .NET Framework version 4.5.2
·        Microsoft SQL Server 2012 Native Client
·        Microsoft WCF Data Services 5.6
·        Microsoft Information Protection and Control Client (MSIPC)
·        Microsoft Sync Framework Runtime v1.0 SP1 (x64)
·        Windows Server AppFabric 1.1
·        Cumulative Update Package 7 for Microsoft AppFabric 1.1 for Windows Server (KB 3092423)
·        Microsoft ODBC Driver 11 for SQL Server
·        Update for Microsoft .NET Framework to disable RC4 in Transport Layer Security (KB2898850)
·        Visual C++ Redistributable Package for Visual Studio 2012
·        Visual C++ Redistributable Package for Visual Studio 2015
In this blog post, I am using pre-requisite tool that comes with SharePoint setup to configure my server.

Installing Pre-requisites

Run setup as administrator, and choose install software pre-requisites.
1.  
2. 
3.
4. 
5. After restart, the pre-requisite tool will resume with remaining installation.
6. Summary screen will show status as below:

At the end of installation, go through the completion status screen as above to identify if any pre-requisite got failed while installation

Installing SharePoint Server 2016:

Choose Install SharePoint server from setup dialog, and follow the screen shots to complete the installation process.
1.
2   2. Accept the agreement check-box, and continue:
3. Choose a file location, if it’s different then the default location mentioned:

4. 
5. At the end of installation of setup binaries, run the configuration wizard to complete the configuration and create farm:

6. 
7. Choose create a new server farm to create a new SharePoint 2016 far. Connection to an existing farm option can be used to join new server to an existing farm.

8. Define the required configuration fields below and proceed:

9    9. Pass-phrase is important, so define and save it somewhere to refer later if required. As it would be required to add another server to scale up your existing farm.
10. Below screen is part of new enhancements/change to SharePoint 2016 deployment process. This will let you choose your server role within a farm, earlier it was all about manually setting up a required application services based on server role in a farm.
11. And the final configuration dialog box let you choose port number for your Central Admin site:

12. Configuration summary page:
 
13. Below step may take a while to complete:

14. At the end of successful configuration, you will be presented with summary configuration. Click finish to launch Central Administration website:
15. Once Central Administration site launched, you can choose wizard to configure services


16. Another change to SharePoint 2016 deployment process is that Project Server is now part of same SharePoint installation as service application.
Project Server always was an application service in SharePoint, but previous versions requires separate set of setup files to be installed to enable Project Server application service in existing SharePoint farm.


17. And here you have a shiny new SharePoint Server 2016 farm ready for you to explore J

More to come soon, keep visiting my blog.

via All about Enterprise Project Management (EPM) http://bit.ly/1QwEu2p

Khurram Jamshed
The author of the blog has an extensive experience of working as an EPM Consultant. Currently he is located in Dubai, UAE and working for Microsoft partner organization as Project Server specialist. He has a thorough experience of providing Project Management technical/functional consultancy to all sort of organizations. He is a certified PMP, a Project Server MCITP, and also received a MS community contributor award 2011.

This article has been cross posted from khurramjamshed.blogspot.com/ (original article)

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

December 9, 2015 Leave a comment
Paul Mather
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011.
I am also a certified Prince2 Practitioner.

This article has been cross posted from pwmather.wordpress.com (original article)

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

http://bit.ly/1NaR2rX

Project 2016 December 2015 update:
http://bit.ly/1IE0nK1

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

http://bit.ly/1NaR2rX

Project Server 2013 December 2015 CU Server Roll up package:
http://bit.ly/1NaR5nw

Project Server 2013 December 2015 update:
http://bit.ly/1IE0mpm

Project 2013 December 2015 update:
http://bit.ly/1NaR5nA

Also worth noting, if you haven’t done so already, install Service Pack 1 http://bit.ly/1uorn2C first if installing the December 2015 CU.

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

http://bit.ly/1NaR2rX

Project Server 2010 December 2015 CU Server Roll up package:
http://bit.ly/1NaR5nC

Project Server 2010 December 2015 update:
<no specific Project Server 2010 update>

Project 2010 December 2015 update:
http://bit.ly/1IE0nK5

SP2 is a pre-requisite for the Office 2010 December 2015 updates.

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

Categories: Paul Mather, Work Tags:
Follow

Get every new post delivered to your Inbox.

Join 491 other followers

%d bloggers like this: