Archive

Posts Tagged ‘Project Server 2010’

More #SharePoint / #ProjectServer 2010 Service Pack 2 details #SP2010 #PS2010

So I see my fellow bloggers Paul and Khurram posted about Service Pack 2 for SharePoint and Project Server 2010.

Having looked around the blog-o-sphere, I came across some extra information that I believe will be useful to all:

Known issues when you install Office 2010 SP2 and SharePoint 2010 SP2
http://support.microsoft.com/kb/2687520

In particular if you are installing Office 2010 SP2 on Windows Server 2003 (SP2) you will need to install this patch first: http://support.microsoft.com/kb/925336 

For SharePoint Server SP2 on Windows Server 2008 R2, you need to be careful of your custom XSL views from SharePoint Designer.  Apparently they break but the fix is already available and it is recommended to install the June 2013 CU (or later) on top of the SP2

Links for June 2013 CU for SharePoint 2010:

The Full Server Packages for June 2013 CU are available through the following links:

After installing the fixes you need to run the SharePoint 2010 Products Configuration Wizard on each machine in the farm.

Locations of all the SP2 download packages around SharePoint, Project Server, FAST, Office Web Apps, Office 2010 products etc…

Next up is that we of course need to consider the different products that we have installed in our farms.  Do we have FAST or Office Web Apps?

This link will help: http://support.microsoft.com/kb/2687522

Further links are available here, including Office, Project, Visio, SharePoint Designer and the CSOM binaries:

    I haven’t seen a service pack 2 for the language packs yet, but will update if it comes up soon.

Changes for SharePoint / Office 2010 SP2 that are not in Cumulative / Public Updates

Handily Microsoft have also released a spreadsheet detailing the changes and additions as part of Service Pack 2.  Be aware that these are not included in any previous CU / PU.

http://support.microsoft.com/kb/2687453

 

Ok, hopefully you will all find the above useful.  Till the next time…

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.

image

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.

image

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

From the MSP_EpmProject_UserView view in the reporting database

image

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:

image

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!

OLAP Cube Error – Cannot process the Project custom field

June 27, 2013 1 comment

Just a quick note to let you know about an error I came across today.

In Project Server 2010, I had a field called “Objective”. This was associated with a lookup table of the same name, which was single-value select. This field was added to the Project OLAP cube, which built successfully. So far so good!

I then changed the field type to multi-select, and left the cube to build overnight. Came back the next day to a failed OLAP build. The exact error I got in the queue was this:

  • CBS message processor failed:
  • CBSMetadataProcessingFailure (17005) – InitCustomFieldDimensions cannot process the Project custom field ‘Objective’. Details: id=’17005′ name=’CBSMetadataProcessingFailure’ uid=’c69b0459-5d1f-4d78-a410-f56cd32eca97′ QueueMessageBody=’Setting UID=00007829-4392-48b3-b533-5a5a4797e3c9 ASServerName=<SQLServer> ASDBName=OLAPCube ASExtraNetAddress= RangeChoice=0 PastNum=1 PastUnit=0 NextNum=1 NextUnit=0 FromDate=10/30/2012 00:00:00 ToDate=10/30/2012 00:00:00 HighPriority=True’ Error=’InitCustomFieldDimensions cannot process the Project custom field ‘Objective”.

Hmmm…OK, must be the change I made to the field. I need this field to be multi-value, but I don’t necessarily need it in the cube for reporting. So, I went to remove the field from the cube but it wasn’t listed. Weird. I thought re-saving the OLAP configuration and re-building it would just flush out the field since it was no longer listed in the cube configuration. I got the same error in the queue again.

The only fix I found for this was to re-create the OLAP cube with all of the same settings as previously, minus the “Objective” field, which I couldn’t add anyway as multi-value fields aren’t available to add to the cube.

Hope this helps you out if you come across this error in the future.

Lester

Edit: it seems that this was a known issue back in 2011, which hasn’t yet been fixed. More info on Brian Smith’s blog here: http://blogs.msdn.com/b/brismith/archive/2011/02/04/project-server-2010-take-care-changing-custom-fields-to-allow-multiple-values.aspx

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

image

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

 

image

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();

    ctx.executeQueryAsync(
       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() {
    alert("failed");
}

getWebProperty();

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();
    ctx.load(this.web);
    ctx.load(this.props);

    ctx.executeQueryAsync(
       Function.createDelegate(this, gotProperty), 
       Function.createDelegate(this, failedGettingProperty)
    );
}

function gotProperty() {
            //alert(props.isPropertyAvailable('allowdesigner'));
            for(var itm in this.web){
                        console.log(itm);
            }
            for(var prop in props){
            console.log(prop);
            }
            for(var fv in this.props.get_fieldValues())
            { 
                        console.log(fv);
            }
            alert(this.props.get_fieldValues()["MSPWAPROJUID"]); 
}

function failedGettingProperty() {
    alert("failed");
}

getWebProperty();

 

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="http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js" />

 

Presenting and staffing at TechEd Europe 2012 next week #TEE12

Just a quick blog post to say that I will be presenting at TechEd Europe 2012 next week with my slide deck:

Integrating Project Server & SharePoint 2010
 Deployment Approaches, Integration Options
& making the most of the SharePoint Enterprise Features

TechEd Europe 2012

Code: OSP02-LNC

  • Level: 300
  • Category: Office, Office 365 & SharePoint
  • Presenter: Giles Hamson
  • Date: Wednesday, June 27th 2012
  • Time: 13:30 to 14:15 (45 mins)
  • Location: Hall 2

The key focus of this session is to understand three popular approaches to implementing SharePoint and Project Server together and the key benefits to each method.

In addition you will also learn:

  • Understanding how SharePoint and Project Server work together
  • Using the enterprise features of SharePoint to leverage Project Server data
  • How SharePoint and Project Server techniques differ and can cause issues with implementation

I will also be staffing the Microsoft stand to discuss Project Server, Project, SharePoint & Office with anyone who stops by.  So if you have any questions about the product set or you just want to say hello, come along.

My Schedule:

  • Tuesday: Booth 13:30 till 15:30
  • Wednesday: Presentation 13:30 till 14:15 (link)
  • Flight out Wednesday night – Airport for 7pm ish.

Look forward to seeing you there!

Project Conference 2012 video presentations now available #PS2010 #ProjectServer #MSProject #in

PC2012_Sig_160x98_Speaker

Over the past couple of months, you may have seen posts about my presentation at the Project Conference held in Phoenix, AZ.   Now that some time has passed, Microsoft has uploaded all the video presentations to the Project channel on Microsoft Showcase.

The Project team officially announced the availability here.

CPS_Group_logo_rgb

As part of the Microsoft Project Conference 2012, Corporate Project Solutions (my company) not only sponsored my presentation, but also the client I have been working for over the last couple of years, ARM.

So without further ado, I offer both video presentations for your consideration:

image

URL: http://www.microsoft.com/en-us/showcase/details.aspx?uuid=06fff348-8836-497b-a5eb-b5ed63a3b6c9

image

URL: http://www.microsoft.com/en-us/showcase/details.aspx?uuid=17a5610c-8d0f-49f2-869c-d6d1021d472a

View Ghamson's profile on slideshare

If you would like to skim through the slides, I have uploaded them to SlideShare for your convenience:

Integrating SharePoint and Project Server 2010

8 Billion Reasons… Why ARM Chose Project Server 2010

Enjoy and if you have any questions about the above or would like to know more, please get in contact!

Using the “Inactivate Tasks” functionality

Inactivate task is a new feature for EPM2010; this feature enables the project manager to set certain tasks to inactive rather than deleting the tasks. This functionality is also useful for performing what-if analysis.

The following paragraph from Microsoft explains that intended usage of the inactivate task functionality:

“Microsoft Project Professional 2010 enables you to cancel a task but keep a record of the task in the project plan. This is called inactivating the task. The task remains in the project plan, but does not affect resource availability, the schedule or how other tasks are scheduled. Note: Inactivating a task is a feature available only with Project Professional.
Why would you want to inactivate a task? For one thing, it can help you model the effects of schedule or resource constraints on the project without deleting tasks permanently. Also, inactive tasks remain in the project plan, providing a record of cancelled tasks and enabling you to reactivate them if circumstances change.
Note: Inactivation is nor a good way to archive complete tasks, because it could have unanticipated effects on the remaining schedule. Instead, mark the tasks as completed.”
http://office.microsoft.com/en-us/project-help.inactivate-a-task-HA010370341.aspx

Please see the following best practise guidelines for using inactive tasks:

  • When in the planning phase, if you decide that a task or tasks are not required, at this stage use the inactivate task feature to set tasks to inactive rather than deleting the tasks. this will give you the option to quickly make these tasks active at a later date if there is a requirement for these tasks.
  • Inactive tasks do not affect resource availability. Baseline values that have already been taken are retained, but any new baselines taken will not include data for inactive tasks.
  • Tasks that have actual work cannot be made inactive.
  • Inactive tasks are not published, so inactive task assignments will not appear on a team member’s task list.
  • Inactive tasks are available to report on via the Project Server OLAP cube, so care should be taken when reporting that these tasks are/aren’t included depending on the figures required. The “Task is Active” field  can be used to include or exclude inactive tasks. If you do not see this field in your OLAP cube, it may be that the EPM administrator has not enabled inactive tasks in the cube.

#SP2010 #PS2010 Performance Links

Some useful links for Capacity Performance and Management

SharePoint 2010

Capacity management and sizing overview

http://technet.microsoft.com/en-us/library/ff758647.aspx

Software boundaries and limits

http://technet.microsoft.com/en-us/library/cc262787.aspx

Performance and capacity test results / recommendations

http://technet.microsoft.com/en-us/library/ff608068.aspx

Performance and capacity technical case studies

http://technet.microsoft.com/en-us/library/cc261716.aspx

InfoPath Form Services – performance and capacity requirements

http://technet.microsoft.com/en-us/library/gg576954.aspx

 

Project Server 2010

Plan hardware architecture

http://technet.microsoft.com/en-us/library/hh297440.aspx

Software Boundaries (Project Server 2007)

http://technet.microsoft.com/en-us/library/cc197693(v=office.12).aspx

SSRS Web Part Performance 2008 R2 vs. 2012 Initial Results #SharePoint #SP2010 #in

April 30, 2012 11 comments

On one of my client projects, we heavily use SQL Server Reporting Services in SharePoint integration mode.

The benefits in comparison to Native mode are primarily around the RS SharePoint Add-in which allows us to use query string (URL) filter web parts to pass parameters to reports and create powerful dynamic dashboards as well as using SharePoint to permission and store the reports.

There is an issue however.  Performance in this mode is not amazing, as detailed here:

Now that SQL Server 2012 has gone to RTM, we can start to get a measure of how well the new web part performs and I am pleased to say that the improvements appear to be great so far…

The Scenario

  • SharePoint Version: 2010 SP1 – December 2011 CU with Project Server
  • DB Server: SQL Server 2008 R2 SP1
  • SSRS Version: 2008 R2 SP1
  • SSRS Add-in: 2012 (Denali) – RTM
  • Server Architecture: 1 x WFE / App Server (Virtual) + 1 x SQL Server (Virtual)

NB: All testing has been carried out on our DEV server, please always try out new software on a development / test environment first to ensure the benefits and to safe guard production from issues.

The Reports:

Table based reports rolling up Project Server and SharePoint data based on parameters provided by the end user (Cannot show due to client confidentiality I’m afraid).

The Results:

Now this is just a teaser really since we will be doing full testing on our master development environment, but for now…

Project Portfolio Table Report

  • Number of returns items: 17 rows
  • Number of parameters: 1 (Portfolio ID)

SSRS2008R2vs2012

NB: All time taken in seconds using Fiddler2

SSRS2008R2vs2012_ProjectPortfolioWholePage_Graph SSRS2008R2vs2012_ProjectPortfolioSSRS_Graph
SSRS2008R2vs2012_ProjectPortfolioWholePage_Pie SSRS2008R2vs2012_ProjectPortfolioSSRS_Pie

As you can see, we are seeing significant time increases with the new web part and within my client we have the go ahead to carry out further testing.

More useful links:

#SP2010 web part rounded corners #SharePoint #PS2010 #ProjectServer #MSProject #in

April 25, 2012 7 comments

At one of my clients I was asked to document how we achieved rounded corners on web parts. So as a result, I figured a blog post about it would be useful.

Now when I first implemented this (almost 2 years ago!) as the 2010 product RTM’d, I based it on the only blog post around at the time:

    The end result looks like this:

ChromeTitleAndBorder

NB: Please note that this version is slightly modified from the version supplied on the blog link above.

In my implementation I was using the jQuery version available at the time:

  • jQuery 1.5.1
  • jQuery UI 1.8.13

Although jQuery UI is not required, it is always good to have for those awesome calendar pop-ups just in case.

This may work with the newer versions of jQuery, but I haven’t tried it out yet.

Example CSS, JavaScript and rounded corner image files are provided at the bottom of the post.

So without further ado, lets go through how to achieve the rounded corners in SharePoint 2010:

What does the code actually do?

With every page refresh, the JavaScript code, determines where all the web parts on the page are and injects appropriate mark up (<DIV>) above and below each web part, ready to be styled by CSS.

Step 1. Upload your reference files

Personally I like to store all my custom files within the Style Library within SharePoint, but they can live anywhere within SharePoint as long as all users have read access to them.

So lets take a look at what we are storing.

Standard Plug-In Files:

  • jquery-ui-1.8.13.custom.css
  • jquery-1.5.1.min.js
  • jquery-ui-1.8.13.custom.min.js

You can download this version here:

The latest versions are available here:

Custom Files

  • <custom JavaScript file>.js
  • <custom CSS file>.css

These files are where we will implement the JavaScript and CSS code to produce the rounded corners on each web part.

Corner Image Files

The following files are used to create the rounded corner affect. To keep multi-browser support we are using this method, but you could replace them with CSS3 styling by changing the CSS code to achieve the same result.

  • WPBottomLeft.gif
  • WPBottomRight.gif
  • WPTopLeft.gif
  • WPTopRight.gif

Example files are provide below.

Step 2. Add your Master Page file references

Initially add the following references into <head> section of your Master Page, preferably just before the end tag </head>

<link type="text/css" href="/Style Library/jquery-ui-1.8.2.custom.css" 
rel="Stylesheet" />

<script src="/Style Library/jquery-1.4.2.min.js" 
type="text/javascript"></script>

<script src="/Style Library/jquery-ui-1.8.2.custom.min.js" 
type="text/javascript"></script>

Now the above references are just standard plug-ins available from the jQuery website, but we also need to add some of our own JavaScript / jQuery magic, which of course needs its own reference file.

<script src="/Style Library/<customJavaScriptFile>.js" type="text/javascript"></script>

We also need to reference a custom CSS file, so that we can associate the corner images we will be using etc…

Publishing Feature enabled?

Now if you are using the Publishing feature, you can place your custom CSS via the Site Settings interface:

Site Actions > Site Settings > Under Look and Feel – Click “Master Page”

Under the “Alternate CSS URL”, enter the URL for your custom CSS file, for example:

  • /style library/<customCSSFile>.css
    NB: This will ensure it is the last CSS file referenced within the Master Page to allow for overrides.

Publishing Feature not-enabled?

If you you do not have the publishing feature enabled (Office 365 P1 or SharePoint Foundation 2010 for example), you can add the reference into the Master Page also.

<link type="text/css" href="/Style Library/{customCSSFile}.css" 
rel="Stylesheet" />

Step 3. Adding the code

So now that we have our JavaScript, jQuery and CSS files setup in the Master Page, we can edit out custom files with the following code:

CSS Code (customCSSFile.css)

/* Web Part Chrome Styles – START */

.wpContainer {
padding-bottom:0px !important;
}
.wpTitleBorder, .wpBorderOnly {
background-color:#fff !important;
border-left:1px solid #c6c6c5 !important;
border-right:1px solid #c6c6c5 !important;
}
.ms-WPHeader td {
background-color:#ffffff !important;
border:0 !important;
padding:0 !important;
padding-top: 3px !important;
border-bottom: 1px #CECFCE solid !important;
}
h3.ms-WPTitle {
/* color:#36424a !important; */
font-size:15px !important;
font-weight:normal !important;
margin:-3px 0 0 0px !important;
padding:0 14px 4px 4px !important;
}
h3.ms-WPTitle a {
/* color:#36424a !important; */
font-size:15px !important;
font-weight:normal !important;
}
h3.ms-WPTitle nobr {
white-space:normal !important;
}
.ms-WPHeader td div.ms-HoverCellInActive {
margin:0 !important;
*padding:0 0 2px 0 !important; /* IE <8 fix */
}
.ms-WPHeader td .ms-HoverCellInActive {
margin:0 !important;
*padding:0 0 2px 0 !important; /* IE <8 fix */
}
.ms-WPHeader td .ms-HoverCellInActive img {
margin:0 0 2px 0 !important;
*margin:0 !important; /* IE <8 fix */
}
.ms-WPHeader img.ms-HoverCellInActive { /* Firefox */
padding:0 0 2px 0 !important;
}
.ms-WPHeader td .ms-HoverCellActiveDark {
border:0 !important;
margin:0 !important;
padding:0 0 2px 0 !important;
}
td.ms-WPBorder, td.ms-WPBorderBorderOnly {
border:0 !important;
padding:0px 0px !important;
}
.ms-WPBody {
font-family:Tahoma, arial, sans-serif !important;
font-size:11px !important;
padding:0 !important;
}
.ms-WPBody td, .ms-WPBody TD DIV, .ms-WPBody TD DIV A {
font-family:Arial, Tahoma, sans-serif !important;
font-size:11px !important;
}
.wpCornersTop {
background:url('/blog/Style Library/Images/WPTopRight.gif')
 top right no-repeat !important;
height:10px !important;
padding-right:10px !important;
}
.wpCornersTop div {
background:url('/blog/Style Library/Images/WPTopLeft.gif')
 0 0 no-repeat !important;
height:10px !important;
}
.wpCornersBtm {
background:url('/blog/Style Library/Images/WPBottomRight.gif')
 bottom right no-repeat !important;
height:11px !important;
padding-right:11px !important;
}
.wpCornersBtm div {
background:url('/blog/Style Library/Images/WPBottomLeft.gif')
 0 0 no-repeat !important;
height:11px !important;
}

/* Web Part Chrome Styles - STOP */

JavaScript / jQuery Code (customJavaScriptFile.js)

function wrapWebParts() {

//Find all divs (div.ms-WPBody) with an ID beginning
//with "WebPart". All web parts have unique IDs assigned
//to them, and they begin with "WebPart". Then traverse up
//the HTML document 4 levels and add the class "wp".

  $('td[id*=MSOZoneCell_WebPart]').children("table").addClass("wp");

//For web parts with the Title and Border chrome,
//add the class "wpTitleBorder" to the element
//with class "wp".

  $(".ms-WPBorder").parents(".wp").addClass("wpTitleBorder");

//For web parts with the Border Only chrome, add the class
//"wpBorderOnly" to the element with the class "wp".

  $(".ms-WPBorderBorderOnly").parents(".wp").addClass("wpBorderOnly");

//Find all table cells that have an ID beginning with
//'"MSOZoneCell" and add the class "wpContainer".

  $("td[id^=MSOZoneCell]").addClass("wpContainer");

//For web parts with the chrome type Title and Border or Border Only,
//add containers that can be used for rounded corners and other
//treatments

  //alert($(".wpTitleBorder").length);
  $(".wpTitleBorder").before('<div class="wpCornersTop"><div></div></div>')
     .after('<div class="wpCornersBtm"><div></div></div>');

  $(".wpBorderOnly").before('<div class="wpCornersTop"><div></div></div>')
     .after('<div class="wpCornersBtm"><div></div></div>');

  $("img[src*=/_layouts/images/blank.gif]")
    .attr("style", "display: none;");

  $('div[class=wpCornersBtm]').each(function() {
    var mainWPTable = $(this).prev();
    var inlineWidthStyle = mainWPTable.attr("style");
    var realWidthSplit = "";
    var realWidth = "";

    if (inlineWidthStyle != undefined) {
      realWidthSplit = inlineWidthStyle.split(":");
       realWidth = realWidthSplit[1].toLowerCase();
       realWidth = realWidth.replace("px", "");
       realWidth = parseInt(realWidth, 10);
       realWidth = realWidth + 13;

       $(this).attr("style", "width: " + realWidth + "px");
       $(this).prev().prev().attr("style", "width: "
          + realWidth + "px");
    }

  });

}

$(document).ready(function(){
   wrapWebParts();
});

And Finally…

The end result is this:

ChromeTitleAndBorder

If we break this down, the jQuery code has discovered each web part on the page, added a <div> above and below the web part and then the CSS has styled it with the supplied image files referenced in the style sheet.

WPImageExample

The code also takes into account the chrome type being used on the web part:

This results in the following:

Chrome Type: None

ChromeTypeNone

Chrome Type: Title and Border

ChromeTitleAndBorder

Chrome Type: Title Only

ChomeTypeTitleOnly

Chrome Type: Border Only

ChromeTypeBorderOnly

Code Downloads:

Follow

Get every new post delivered to your Inbox.

Join 577 other followers

%d bloggers like this: