Information | Business | Technology

PerformancePoint Services for SharePoint

In January Microsoft announced that PerformancePoint Server 2007 would be bundled in SharePoint 14, the much-anticipated next release of SharePoint. They have plans of releasing SP3 for PerformancePoint in mid-2009, but this will be the last major software update for PerformancePoint as a standalone product.

PerformancePoint is Microsoft’s BI platform that is built on the familiar SharePoint framework. It’s basically a customized version of SharePoint that is tailored for customers who need more advanced BI solutions for their organization. PPS generally has two major functions, Monitoring & Analytics and Planning. The M&A piece allows us to create dashboards with any number of analytics for scorecards and charts. The Planning portion is related to budgeting and financial forecasting. The main problem with this product is that it isn’t utilized by that many companies with MOSS 2007 licenses. The added expense for another server product is not practical for most organizations in this economic climate. To make matters worse, MOSS 2007 has a very basic set of BI tools builtin that often makes it hard to upsell on the more useful tools since they are a standalone product.

Microsoft has realized this shortcoming and has decided to combine both products in the next iteration of SharePoint. Unfortunately, this has led to the axing of the integration of the Planning portion of PPS into MOSS. You can still get support from Microsoft on this if you already have PPS standalone, but it will not be integrated into SharePoint 14.

The Bottomline:

This is a logical step for Microsoft’s BI group as PPS and MOSS seemed to have similar goals with competing platforms. If all goes as announced, the next version of MOSS will have even greater BI capabilities […]

By |March 13th, 2009|Categories: Business Intelligence, SharePoint|Tags: , , , |2 Comments

Sharepoint Update Log – Part 2

Part 1 Part 2

In Part 1 of this article I compared and contrasted the various methods that we could use for our Sharepoint update log application. I’ve chosen the custom aspx site/SQL table method as it is the most effective solution for what I currently need. I don’t intend to design a full-fledged application with reporting features, logins, AJAX menus(well.. maybe a little AJAX would be cool!), etc. I need a custom site that is independent of Sharepoint, so developers/admins can log their updates to the database. If Sharepoint breaks, then we should be able to access this data as it might help us determine the point of failure. Simple and effective.

My aspx site is uber-simple to the point to where you might question why I even spent time writing this article. Well, I’m glad you’re that concerned about my free time! I’m writing this, because I see a lot of IT shops without something like this. Keeping an update log for live servers should be a non-negotiable in your environment. I hope that this example will either offer you a solution that you can use immediately or provide you with a catalyst to design your own solution based on your needs. You don’t have to be a VB.NET guru to get this done. For this article, I’ll show you some screenshots, so you can laugh at see how simple this is.

sp_update_log1

  • As you can see I have a few drop down boxes and text boxes that match the table layout from the
By |December 18th, 2008|Categories: SharePoint|Tags: , , , , , |1 Comment

Sharepoint and Search Server 2008

The amazingly kind and helpful folks over at Bamboo Solutions, a leading SharePoint web part/solutions developer, has allowed me to write guest articles on their Bamboo Team Blog. The subject of this post, Sharepoint and Search Server 2008, is my first post there.

Please read the full post here.

While you’re there, I strongly suggest spending some extra time browsing. Bamboo Nation, their community site, is a hidden treasure in the SharePoint community. They have a very active team of content writers that will keep you going back for more.

By |October 14th, 2008|Categories: Search, SharePoint|Tags: , , , |0 Comments

How to: Hide the title column from Sharepoint lists

A frequent request from end-users is the ability to remove the “title” column from Sharepoint lists and document libraries. You can rename this column to something else, but I do not recommend this for various reasons. “Title” is a reserved Sharepoint word and renaming it has been known to break things. Generally this only occurs if you change it in the Site Content Type Gallery, but I tend to err on the side of caution here. You can read about that particular limitation here.

But you can hide the title column from the default content types already built in to Sharepoint with a few easy steps. I’ve posted ample screenshots below for the visually stimulated!

Step 1. Navigate to the desired list that needs to be configured. I am starting with an out-of-the-box Sharepoint task list that has not been configured in any way. You can do the same or start with a custom list.

Step 2. Click on Settings and then List Settings. Once on the settings page for your list, click on the advanced settings link as shown below.

Step 3. The advanced settings page is not all that advanced as there are some common settings here, but you will need to set “Allow management of content types” to yes before proceeding. Click OK to continue.

Step 4. You should see the Content Types section now which will allow you to edit all settings pertaining to the content type that […]

By |August 27th, 2008|Categories: SharePoint|Tags: , , , , , |11 Comments

Sharepoint Update Log – Part 1

Part 1 Part 2

It’s not everyday that you find a company or IT department that keeps a structured and updated “update log” for their systems, let alone Sharepoint. Updating your software is as easy as clicking a few buttons and trusting that everything will work as advertised. And for the most part, application updates really do what they are supposed to without causing outages. With communities, blogs and wikis for just about every application in existence, developers find it much easier to distribute test builds to the masses and receive responses rather quickly. This translates to quicker bug fixes and an overall better experience for end-users. But this can also lead to an ultra-trusting mentality when it comes to updating your software with major upgrades and/or patches. It only takes one patch to create hours of work for you and your team to get the system back online when incompatibilities rear their ugly heads.

This three part article will aim to give you my thoughts for an effective update log for your Sharepoint servers.

NOTE: I’ve written this article with respect to Sharepoint specifically. It is part of a larger concept that could be incorporated into all LOB systems.

The first thing that we need to do is figure out where we should store our data. Depending on your needs and organizational size this may be a very simple setup, but it still helps to think it through first.

The table below summarizes a few pros and cons for 4 possible scenarios.

This is a pretty self-explanatory table, but I want to touch on one of these […]

By |August 21st, 2008|Categories: SharePoint|Tags: , , , , , |1 Comment