Posts Tagged ‘Project Server 2013’

Presenting @HSPUG Transitioning from #SP2013 to #PS2013 for #EPM / #PPM November 20th 2013 #MSProject #ProjectServer

November 11, 2013 Leave a comment

One of my first tasks at BrightStarr is getting myself known in the area and what better way than to start presenting at the local user groups.  So without further ado:

Transitioning from SP to PS for Enterprise Project Management

Presenter: Giles Hamson

As a Project Manager, challenges exist with determining what are the best tools to use to help you be most effective. Project Server and SharePoint are two different tools for Project Management that include their advantages and disadvantages.

In this session, you will come away with the following information:

        • A high level understanding of how SharePoint and Project Server work together
        • The benefits of enterprise project management
        • Project management maturity expectations as solutions become increasingly more complex

        About Giles Hamson

      Giles Hamson has been working with collaboration technologies since 2001 and has been implementing SharePoint solutions from 2004; starting with SharePoint Portal Server 2003 whilst working in the Microsoft Dynamics division in Reading, UK.

      Giles has worked in multiple roles throughout his career working as a business analyst, moving into system analysis and development roles.BrightStarr_SmallLogo

      After gaining experience across Linux, Solaris and Microsoft disciplines, Giles moved into consultancy within the education market creating learning platform solutions based on SharePoint and integration with 3rd party vendors. After several successful implementations Giles moved into consultancy in SharePoint and Project Server across multiple industry verticals.

        Giles has recently moved from the UK to Austin, TX and joined BrightStarr.

      Also being presented at the November H-SPUG meeting is:

        H-SPUG Logo


          Bringing it all together with the Content Search Web Part

          Presenter: Paul McCollum

          Finally take full advantage of the power of search. Construct powerful IT Pro solutions using the Content Search Web Part, Keyword Query Language and the new query builder. Gain perspective on enterprise-wide events and content from a single location.
          About Paul McCollum

          A very early computing adopter, Paul has been programming for more than 30 years, writing his first lines of code in the 2nd grade. The past 20 years have been focused on the Portal space starting by hand with Notepad and Vi. 7-ElevenHe hopped over to SharePoint in 2007 and hasn’t looked back. More recently his role is as an Enterprise Solution Architect and Platform Manager at 7-Eleven. His current focus is around empowering power users and IT pros with rapid development solutions without code or with highly accessible JavaScript and jQuery. In his spare time, Paul contributes to technology forecasting news sites and coaches volleyball


          Microsoft Office, 2000 West Sam Houston Parkway South, #350, Houston, TX 77042 (

          Date & Time

          20th November 2013 – 17:30 till 20:00


      If you manage to make it, come up and say hello Smile


    Project Server Start Date Reporting Quirk

    July 11, 2013 1 comment

    I came across a little possible pitfall while generating some reporting for a client, which I thought I should share with the community.


    In Microsoft Project, the Start Date in Project Information defaults to the Start Date of the first task in the plan.


    Obviously this can be changed in the Project Information so that the Start Date of the Project does not necessarily reflect the Start of the first task in the plan, or the Project Summary task.


    So which date does appears in the reporting database? Well, here are the results:

    From the MSP_EpmProject_UserView view in the reporting database


    As you can see, the date from the MSP_EpmProject_UserView displays whatever is set in the Project Information. This might cause some unexpected information in reports, so we need to expand our query to include the date from the Project Summary task:


    So, when writing the specifications for your reports, make sure you’re clear which date the client wants – it’s not unheard of having a plan created a few months in advance of the work being realistically scheduled which might cause this confusion!

    Obviously the clear process-driven workaround is to have your Project Managers ensure that the Start Date in Project Information is updated when scheduling the project!

    #SPSUK slides: Transitioning from #SP2013 to #PS2013 for #EPM #MSProject #SharePoint

    December 9, 2012 Leave a comment

    Thank to all those who attend my presentation yesterday at SharePoint Saturday UK 2012.  There were lots of questions throughout and a thoroughly  engaged audience.


    Presentation Slides

    The slides are now uploaded here:



    Via PowerPoint (Office Web Apps / SkyDrive)



    Video Demonstration

    I also created a video of the demonstration of the day.  This is embedded as part of the presentation and is also available here:


    Transition steps from Simple to Complex in SharePoint / Project Server 2013

    Transitioning from #SP2013 to #PS2013 for Enterprise Project Management #SPSUK #MSProject #SharePoint

    November 30, 2012 3 comments

    Just a quick note to say that I will be presenting at SharePoint Saturday UK on December 8th 2012 on:

    Project Site to Project Management

    Transitioning from SharePoint to Project Server for Enterprise Project Management

    Video Title

    Session Objectives:

    After attending this session you will understand the different tools for Project Management offered with SharePoint and Project Server, including the advantages / disadvantages of each method.

    In addition you will also takeaway:

    • A high level understanding of how SharePoint / Project Server work together
    • The benefits of enterprise project management
    • Project management maturity expectations as solutions become more complex


    • What’s Project Server / Project Online
    • Understanding Project Maturity
    • Supporting Tools
    • Transition – Simple to Complex
    • Demo
    • Decisions – Where to start?
    • Conclusion

    Where, When, How?

    • Conference: SharePoint Saturday UK 2012
    • Location: Nottingham
    • Date: Saturday, 8 December 2012
    • Conference Times: 09:00 to 17:00 (GMT)
    • Presentation Time: 13:30 to 14:30
    • Presenter: Giles Hamson
    • Full Address:

    East Midlands Conference Centre
    University Park
    NG7 2RJ Nottingham
    United Kingdom

    If you see me during the day, say hello and I hope you all enjoy the conference.

    #SharePoint Conference 2012 Opening Keynote #SP2013 #PS2013 #MSProject #ProjectServer

    November 15, 2012 Leave a comment

    Just a quick email to say that the Opening Keynote from the SharePoint Conference 2012 is now available online.

    SPC2012 Opening Keynote

    #SP2013 #PS2013 and Business Intelligence TechNet links

    October 31, 2012 Leave a comment

    Just a few useful links from the newly released / updated TechNet articles around SharePoint, Project Server and BI in 2013

    SharePoint 2013

    Project Server 2013


    Business Intelligence within SharePoint 2013

    Excel Services


    Visio Services

    2012 SP1 CTP4 is out and RS2012 installation details here:

    SQL Server 2012 BI – includes links to Report Builder, Power View and PowerPivot help

    Reporting Services 2012 Developers Reference

    Hardware and Software requirements for Reporting Services and Power View

    Supported Reporting Services with SharePoint combinations

    Reporting Services add-in locations

    Feature support for rs2012 Native vs. SharePoint

    Reporting Services 2012 feature availability comparison with different SQL Server 2012 editions

    Office 2013 Preview Client Requirement #Office365 #MSProject #PS2013 #SP2013

    July 30, 2012 1 comment

    As we gear up further here at CPS with the Office 2013 Preview and what it means for our clients, we started to look client requirements.

    Now many of our larger clients are still running Windows XP and looking at the confirmed clients requirements for the Office 2013 Preview, it would appear Windows 7 and higher now the new standard with Internet Explorer 8 or above.

    In Microsoft’s defence, Windows XP is a very old operating system and we can’t expect them to support it forever.

    To work out when mainstream support ends for your versions of Office and Windows, you and go to the Microsoft Product Lifecycle – Support Home:



    Anyway, on with some of the details I came across:


    Office 2013 Preview App-V (Streaming) Client Requirements

    For those of you using the Office 365 Preview, the Office 2013 / Project 2013 clients that stream down via App-V (Application Virtualisation).  The preview also uses a new version of App-V, version 5.0 beta 2 of which the minimum requirements is also Windows 7 or higher.

    App-V 5.0 Beta 2

    Supported operating systems:

    • Windows 7
    • Windows 8 Release Preview
    • Windows Server 2008 R2
    • Windows Server 2012 Release Candidate

    App-V Packages + Requirements:


    Office 2013 Preview Client Requirements

    Details of the requirements are below.  Specific details by product are at the MSDN link below:

    Component Requirement
    Computer and Processor 1 gigahertz or faster x86- or x64-bit processor with SSE2 instruction set
    Memory (RAM) 1 gigabyte (GB) RAM (32 bit); 2 gigabytes (GB) RAM (64 bit)
    Hard disk 3.0 gigabytes (GB) available
    Display Graphics hardware acceleration requires a DirectX10 graphics card and 1024 x 576 resolution
    Operating System Windows 7, Windows 8, Windows Server 2008 R2, or Windows Server 2012
    Browser Microsoft Internet Explorer 8, 9, or 10; Mozilla Firefox 10.x or a later version; Apple Safari 5; or Google Chrome 17.x
    .NET version 3.5, 4.0, or 4.5
    Multi-touch A touch-enabled device is required for any multi-touch functionality. However, all features and functionality are always available by using a keyboard, mouse, or other standard or accessible input device. Note that new touch features are optimized for use with Windows 8.

    System Requirements:

    #MSProject – Practice makes Perfect #ProjectServer #Office365

    During a three day Prince2 Practitioner course with me being a consultant that implements Microsoft Project. I asked the six project managers the following question: “How many of you use Microsoft Project to plan your projects” The responds was as what I expected “I use Excel”, “I only use it to draw up my initial plan and hang it against a wall”. While I do not like Excel as a planning tool, I can understand a lot of Project Managers use it.

    My follow-up question is then do you update your plan on a weekly basis. The answer I usual get then is no. I have it in my head and update the plan when I need to (which usual takes a lot of time).

    This is an example on what I see on day to day basis. There are still a lot of Project Managers that use Microsoft Project to make a plan and then never use it again to update it.

    My question would be why? Microsoft Project has great functions that a Project Manager can use to make it a really easy job to update a project plan. I think the answer lies in that a lot of Project Managers do not take the time to explore Microsoft Project and it’s functions and features.

    The next question would be is it really needed? I suppose not and depends on your style as a Project Manager, but what I do know is, that it can really save you a lot of time and effort. And that as a Project Manager is what we all want. We have a lot of things to do on a daily basis anyway.

    To help any Project Manager that is interested in Microsoft Project and use it  or wants to start using it for their projects, I am going to start a series called “Practice makes Perfect” that will try to help to get the most out of Microsoft Project. For the series I will use Microsoft Project Professional 2010 or the new Project Professional 2013 (currently part of the Microsoft Office preview).

    Microsoft Project 2010

    This series will include for example:

    • Baseline usage
    • Views (Think of easy views a project manager can use to update their plan)
    • Reports

    I hope that this series will help Project Managers to get more out of Microsoft Project and really help them on a day to day basis.

    Robin Kruithof
    I am Robin Kruithof. I am working at CXS in the Netherlands as a Microsoft Project Consultant. My passion lies in Project Management and everything in the Project Management domain.

    This article has been cross posted from

    Retrieving the Project GUID with JavaScript CSOM #PS2013 #PS2010 #MSProject #Office365 #in

    July 20, 2012 5 comments

    So the Microsoft Office preview is out and unfortunately my colleagues and I are still consulting on current and previous versions, so only limited time around client work allows for play.  Luckily we have had access to earlier versions for several months now so as a company Corporate Project Solutions is prepared for 2013 and we are even running knowledge sessions and upgrade validation checks.

    Moving on… whilst in the hotel, we started playing with Napa and the possibilities around what can and can’t be done.

    Although this example is not relevant to Napa (due to the environment the apps run in), we did manage to product some code that would be useful for Sandbox Solutions or Composite solutions using the Content Editor Web Part in Project Online, Project Server 2013 and potentially Project Server 2010.

    In this example, we use the SharePoint Client Side Object Model to view the property bag within a Project Site to retrieve the following:

    • Internal Project UID
    • Project Wep App URL
    • Project Web App Site UID.

    NB: The Project UID is for the plan associated within to the site in Project Server.

    The Result


    SharePoint CSOM code running within a Project Site in Project Online (Office 365 Preview)



    Closer look at the output


    So you may be wondering, why we need this information.  Well with the introduction of Project Online / Project Server 2013, the client side object model can interact with the PSI to return Project and Resource data.

    In many cases you will need the Project UID as a starting point!

    Here are the details of getting things up and running in the IE Development Toolbar Smile and trust me, there is much more CSOM goodness to come.


    Final Code Example:

    function getWebProperty() {
        var ctx = new SP.ClientContext.get_current();
        this.web = ctx.get_web();
        this.props =  this.web.get_allProperties();
           Function.createDelegate(this, gotProperty), 
           Function.createDelegate(this, failedGettingProperty)
    function gotProperty() {
        alert("Project UID: " + this.props.get_fieldValues()["MSPWAPROJUID"]
         + "\nPWA URL: " + this.props.get_fieldValues()["PWAURL"]
         + "\nPWA Site UID: " + this.props.get_fieldValues()["MSPWASITEUID"]
    function failedGettingProperty() {

    Debug Code Example:

    To get this detail out, me and my colleague had to do some digging in the object model using debug code to alert out to the console values at the Web and Property object areas:

    function getWebProperty() {
        var ctx = new SP.ClientContext.get_current();
                for(var p in ctx)
                            console.log("T: " + p);
        this.web = ctx.get_web();
        this.props =  this.web.get_allProperties();
           Function.createDelegate(this, gotProperty), 
           Function.createDelegate(this, failedGettingProperty)
    function gotProperty() {
                for(var itm in this.web){
                for(var prop in props){
                for(var fv in this.props.get_fieldValues())
    function failedGettingProperty() {


    Example References

    Just in case you need to add sources for JavaScript frameworks.  Here are some references below:

    <script type="text/ecmascript" src="/_layouts/SP.Core.js" />
    <script type="text/ecmascript" src="/_layouts/SP.Debug.js" />
    <script type="text/ecmascript" src="/_layouts/SP.Runtime.Debug.js" />
    <script type="text/javascript" 
         src="" />


    %d bloggers like this: