It is sooo much easier to keep on top of your tasks if you can see at a glance what is due when.

It’s easy to add this color coding to your SharePoint lists with SharePoint Highlighter in just a few clicks, but setting up the rules correctly is a bit of a mind-bender, so in this post we are going to show you how.

So above you can see:

• Tasks due in less than 7 days highlighted in orange
• Tasks due in 7-14 days highlighted in yellow.
• Tasks due in more than 14 days highlighted in green.

So first add a Highlighter column to your list:

http://www.pentalogic.net/sharepoint-products/highlighter/h-manual/h-configuration

Give it a name – I’ve called mine “Due When”.

From the 3 Highlighting Styles choose Highlighting, and choose to Highlight Rows, though this method would work equally well with icons or cell highlighting.

As we are highlighting the whole row we don’t really need to see the actual Highlighter column, so choose to put this to the right of the view, out of the way.

If we were using Auto Setup Rules we would now base the Highlighter column on your Due Date column – this is where it would get its information from.  But what we want to do is a bit too complex for the Auto Setup, so you can leave this box blank and go straight to to the Advanced Rules – click Add Custom.

Scary!  Not really, we just need to think logically about when we are trying to achieve.

The main thing you need to remember is that Highlighter will apply the first rule it finds that is true.  Once it has applied one rule to a row, it will ignore all other rules.

So to get the Highlighting shown above we need this setup:

So, when Highlighter checks the list, first it checks to see if the item’s due date is less than 7 days after today, if it is Highlighter colors the row orange and moves on to check the next list item.  If this rule isn’t met Highlighter checks to see whether the item’s due date is less than 14 days after today, and so on.

It’s all a matter of getting your rules in the right order.  So for example, if we change the order of the rules so the 14 day rule comes first, like this:

This is what happens to the list:

As you can see we have lost our orange highlighting for items that are “Due in Less than 7 days”.  Because Due in less than 14 days is now at the top of our list of rules this is what Highlighter is checking for first, so it is missing the more urgent items.

It’s all about getting your rules in the right order, and as you can see, Highlighter gives you the ability to move items up and down the list with the up/down arrows, or insert or delete a rule at any point.

I hope this has helped to make sense of the advanced rules, and if you have any scenarios that you would like us to work through for you then we would love to hear from you.

So we all like to know how we are doing – hitting our targets, meeting our KPI’s, staying within our budgets, running out of vacation days.

If you record things like this in SharePoint lists you would hope it would be easy enough to see how your actual performance compares to your targets, budgets or KPI’s.

Well for those of you who have Enterprise  and PerformancePoint it is possible – if not exactly a walk in the park –  but for the rest of us this can be a tricky task.   You need to find a way of bringing together 2 different sets of data:

• a Target or KPI - which is one item of data, which stays constant – no one likes a moving target do they?
• and an “Actual” figure which is the sum of a number of list items – sales, purchases, leave bookings, whatever, and which will clearly change as list items are added and changed.

So if we were looking to compare Target and Actual sales for July, as in the chart above, the date would loook like this.  A list of sales items, which will grow as the month progresses, producing a changing Actual total,  and one Target item, which will stay the same throughout the month.

These two data sets would generally live in separate lists.  The way many KPI columns work is by getting you to manually enter – and manually update – your changing Actual total into your Target list.  Not great, as you never get to see how the situation is changing until you have done your manual update.

In a workaround for one of our PivotPoint customers we have turned this on method on its head – entering the static “Target” into the ~Actuals list (in this example the sales list) to allow you to produce a chart or table with our PivotPoint web part, which will show actuals vs targets and is updated as your actual data changes, without the need for manual intervention.

So here’s how.

Add a new column to your list.  Make it a choice column with the choices as “Actual” and “Target”.  Have it default to actual, as this is what the vast majority of items are going to be.

Then we simply enter a “Target” item for each category we want to compare.  So in this example I want to see actual vs target sales for each of my products. So I have entered a Target Sales item for each of my products for July.

As the month goes on my team will enter actual sales for July, which will (hopefully) start to stack up nicely against my target.

So to see how things are shaping up set up a PivotPoint, get it to watch the sales list, and in this case a “This Month” view of the sales list.  Display a Pivot Chart, in this case a column chart.

To see the actual sales vs target sales set it up like this:

• Get your column data from the Actual/Target field.
• Your Row data from the product field.
• And your values from the Value field.

And you should end up with a nice column chart like the one above.

The best bit about this is that your chart will update as your list data changes.  So let’s say I get a really huge Planner order:

Woohoo – you can take that to the bank!

So, it’s not perfect, it’s a workaround, but some of you might find it useful.

Places you could use this would include:

• Sales vs Target
• Budget vs actual expenditure
• Annual Vacation Allocation vs Vacation taken to date.

If you have any other ideas on where this might be useful we would love to hear them.

It’s all too easy to say that a piece of software is “intuitive” or “Quick and Easy” to use. But what’s quick and easy for me could quite possibly be mind bogglingly slow and tricky for you.

So to show you just how quick and easy it really is to set up dynamic Pivot charts and tables in SharePoint using PivotPoint web part we have produced a 4 minute video demo which walks you through the set up.

The video:

• walks you through setting up a pivot chart from SharePoint list data,
• shows you how the chart or table you have created provides a drill-down to a filtered view of your list data, and
• shows you how your charts and tables update dynamically as you list data changes.

Take a look and if you think you could make use of PivotPoint on your SharePoint site why not try it out with a 30 day free trial.

Eagerly awaited v2 of PivotPoint web part for SharePoint is now available for you to try, or buy.

We think you’re going to like this one.

Some of you will be familiar with PivotPoint already; it lets you summarize complex SharePoint list data by creating Pivot Tables.  These update dynamically, as your list data changes. So they are great to use in dashboards for things like keeping an eye on how sales are going, keeping tabs on how your helpdesk is performing, seeing who’s taking way too much sick leave.

People in the finance sector and statisticians have always been really keen on PivotPoint; they understand how useful Pivot Tables are and feel right at home looking at rows of figures all day.  For the rest of us  a nice colourful chart tends to make things easier to understand at a glance, so that’s what we have added to PivotPoint version 2.

As well as creating Pivot Tables, which are linked directly to your SharePoint list data and therefore update automatically as your list data changes, you can also create Pivot Charts, which are also linked directly to the list.  You can choose bar charts, line charts, column charts, funnels, pies – the world’s your oyster!  Color code as you wish, and if you want the visualisation and the detail you can display a chart and a table together.

Another advantage of having the web part directly connected to the list is that we have been able to include drill down, from the chart or table, to a filtered view of the list.  So for example when I am looking at my “Sales by Product, This Month”, chart, I will be able to hover over the enormous, sky rocketing column which represents this month’s sales for PivotPoint version 2, click on it, and go directly to a list view showing just the sales records for all the people who have bought PivotPoint this month – how cool is that?

The new version also has other handy features, like export to excel, so that you can do more analysis on your figures if needed, and easy printing, because we know SharePoint generally isn’t all that print friendly.

If you are an existing customer you can upgrade to v2 without disrupting any of your existing settings.

If you’re not a customer yet, well what are you waiting for?  Take a free trial and see what your SharePoint deployment is missing!

We have just released v1.3.8 of SharePoint Highlighter.

As well as fixing a couple of little bugs, the main advantage of the new version is improved speed and performance.

When we released Highlighter we had looked at its performance on very long lists, ensuring even with number of Highlighter’s visual enhancements applied long lists still loaded and refreshed quickly.

But when we thought about how people would use Highlighter we envisaged them using maybe 2 or 3 Highlighter columns on a list, certainly no more than 10.

What we have found is that quite a number of customers are using far more Highlighter columns on one list than we had ever expected – over 20 in some cases. Having this many Highlighter columns applied to the list was slowing things down.

So for the new release we have worked on performance, so that now you can use just about as many Highlighter columns as you wish on one list and still maintain good levels of speed and performance.

You can download the new version of Highlighter here.

For those of you who, like use, are wondering how you could possibly use over 20 Highlighter columns on one list, the examples we have seen so far seem to be around multiple status indicators. Next week Stuart will post an example use case, showing the kind of scenario where multiple Highlighter columns might be sueful.

A customer for our Highlighter product recently asked us how you could modify SharePoints List View Web Part (LVWP) to word wrap column headers. He had found that as he had replaced lengthy text with status icons he could fit a lot more columns on the page – if only he could shrink the column headers down.

To be clear – this isn’t unique to lists using our Highlighter product, this example shows a basic SharePoint list with a long title that is causing a horizontal toolbar as it won’t word warp even though the column will only ever contain Yes or No.

Of course you could rename the column and shorted the name and put more information in the description – but that only appears on the Edit form so it’s a balancing act between being brief and giving enough info so everyone knows what the columns contains.

Anyway – how to make these columns word wrap?

Inspired by this post on Stack Exchange I looked at using Cascading Style Sheets to do this.

The property we need is white-space : normal

Then we need to figure out which parts of the html to apply it to. This is done by HTML classes, so taking into account SharePoint 2007 and 2010 and different column styles (number/text/filterable/non-filterable) we end up with.

<style type= "text/css">

.ms-vh, .ms-vh2-nograd, .ms-vh2, .ms-vb

{white-space: normal}

</style>

So the white-space property is applied to html elements with a class of .ms-vh, ms-vh2-nograd and so on.

We could also make the column headers center aligned and red (just for an example) by putting in

<style type="text/css">

.ms-vh, .ms-vh2-nograd, .ms-vh2, .ms-vb

{white-space: normal;

text-align:center; 
vertical-align:text-bottom;}

</style>

So how do we add these styles to the page?

You can use SharePoint Designer, but perhaps the easiest way is to add it via a Content Editor Web Part (CEWP)

• Go to your list.
• Select Site Actions > Edit Page
• Click “Add a web part”

And – word wrapping :-

If this doesn’t work for you then as with all things ‘code’ exact syntax is important so check everything carefully – a “ is not the same as a ” for example. Also be sure that you’ve put the CSS in the HTML Source area, not just directly into the rich text editor.

You can add lots more effects (Red, bold etc) but sometimes its hard figuring out exactly what html elements and classes to target (e.g. you can’t apply a colour to the .ms-vh table header, you’ve got to apply it to an anchor element inside this – so “.ms-vh a”) – Firebug, the IE developer tools or the Chrome equivalent are invaluable for this – they will save your sanity!

Calculated columns are a really useful feature of any SharePoint list.

Whether you want to automatically show the profit on a sale, or the financial year that a date falls in to, or tidy up sloppy user input by capitalising names.  There is a lot you can do it with a Calculated Column.

But remembering the formulas and functions needed is not always easy, especially before the first coffee of the morning.  I know there is a way to get rid of the decimal places on a number but is it TRUN, or TRUNC, or TRUNK – oh no, hang on, that last one is just to do with elephants!

So, over the years we’ve gathered together a quick reference of some of the most commonly used functions and formulas – stuck on a wall above the desk it saves a lot of time and head scratching.  We’ve found ourselves sending it to clients from time to time, and they seem to find it quite handy too.

So we decided to tidy it up – clean off the coffee stains and make a nice PDF of it – and make it available to download, free – yes that’s right, FREE!

So why not download our free Calculated Column Cheat Sheet and save yourself some time and headaches?  This easy 3 page reference sheet gives you a selection of commonly used calculated column formulas, along with a pretty thorough reference of most of the functions and operators you are likely to need in your day to day work.

Download, print, stick it on the wall, and we hope you find it as handy as we do!

SharePoint Workflows are one of the magic parts of the solution – the bits when even the most cynical and sceptical end user gets to see the benefit.

Instead of emails and bits of paper flying round your organization, getting lost, forgotten and falling between the cracks, everything is managed and driven centrally by SharePoint.

There are a whole load of scenarios where you could use workflows:

• Vacation approvals
• Expense claims
• Purchase order Authorisation
• Timesheet approvals
• Invoice payment approvals
• Helpdesk escalations

SharePoint can handle all of these processes seamlessly and automatically.  Seeking appropriate approvals, escalating, notifying, referring back and reminding as needed, whilst keeping all documentation secure in one central location.

So, that’s the upside.  The downside is that to create a SharePoint workflow you need to use either SharePoint Designer or Visual Studio.  Whilst SharePoint Designer isn’t all that hard to master it is a very powerful tool and capable of doing serious damage in the wrong hands, for this reason many organizations keep it looked firmly away from most users.  Visual Studio on the other hand really is hard to master – strictly for the mega-brains in your IT department.  So this means that cooking up a bit of Workflow magic out of the box is out of the question for most SharePoint users.

The alternative is to use SharePoint Reminder to create your SharePoint workflows. Using SharePoint Reminder and some clever filtered list views you can easily create multi stage workflows to cover any of the scenarios listed above.

This use case walks you through how to create a 2 stage supplier invoice approval workflow, using SharePoint Reminder and a standard SharePoint document library.

Reminder only drives simple workflow, it doesn’t have the advanced logic of SharePoint OTTB Workflows and it won’t do things like automatically updating lists or other systems.  But for a lot of your day to day processes, you might find that it does just what you need.

If you’ve got a list containing important dates (such as the above example), it’s very useful to be able to easily see how long is left before that date, or how long since it has passed. Unfortunately basing a calculated column on the current date isn’t supported by SharePoint natively, as discussed in my previous article: How to use [Today] in a SharePoint list

So how can we work around this shortcoming without having to wave signs and shout outside Microsoft’s offices? The are a few options available to us:

• JavaScript: Use a Content Editor Web Part.
• Designer: Create a custom view in SharePoint Designer.
• Code: Make your own custom field type from scratch.
• SharePoint Highlighter: Buy our custom field type.

JavaScript

Since SharePoint is so uncooperative about using the current date on the server side (i.e. with a calculated column), we can wait until the information gets to our browser and fix it there with JavaScript.

We can get JavaScript onto a page using a Content Editor Web Part, which is added just like any other web part. Christophe at Path to SharePoint has put together a script that displays the date difference on hover, that can be modified slightly to display just the countdown: Countdowns – A second method

Adding a CEWP to each page your list is displayed on can become quite arduous if it’s displayed in a lot of places. In addition to this, information in a CEWP is quite vulnerable to accidental edits, as they are accessible to any user that can edit page content.

Designer

SharePoint Designer is a free and powerful tool from Microsoft for customizing SharePoint. Unfortunately, because it can do so much, its use is often frowned upon by site administrators (and sometimes even banned).

If you’re lucky enough to be allowed to use it, then (in an unusual twist) Christophe may once again be the person to look to. In a break from his many and various JavaScript solutions he’s put together a Designer solution for this problem too: A countdown for tasks lists

As with the JavaScript solution above, the Designer changes will have to be made on each view web part you want to see the countdown on, but fortunately the changes can only be overridden by someone else using Designer, or an administrator.

Code

If you already have the backbone of a custom field type coded, then adding the XSLT to display this in 2010 should be reasonably straightforward. Alternatively this can be done within the custom field type class.

If you’re using 2007, then CAML rendering unfortunately fails you here, and it’s necessary to use a JavaScript workaround in one form or another.

Creating a custom field type from scratch for this sole purpose is probably going to be remarkably costly (in terms of time). Actually making the foundations of a custom field type is a bit of an investment, but thankfully Microsoft has put together a walkthrough to at least help you get started.

The benefit of using this method is that columns created from a field type are displayed on every page without having to add any additional code to the page itself.

SharePoint Highlighter

Of course, it is possible to get all the benefits of a custom field type with much less pain: Buy a commercial solution.

If you have a glance at out handy product comparison, you can see the wealth of products we managed to find that offer this functionality. So far that grand total is… One: SharePoint Highlighter.

So if you’re looking for a commercial solution it looks like we’re the only option. If you know otherwise then please do tell us; but for the time being we’ll cheerfully carry on being the front-runner in this one horse race.

Whether you call it a KPI, an Indicator, or a Data Visualization Asset, the chances are that you immediately understand the purpose of the icons in the picture above. The beauty of adding icons to a list is harnessing this instant recognition to make your users work more efficiently with their data.

So how do we add icons to our list? This depends very much on how complex and configurable you want he results to be, so let me give you a run down of the options:

Do It Yourself

• JavaScript: Do the work on the client-side with a Content Editor Web Part
• Designer: Customise the list view using SharePoint Designer
• Download: Download an open source Custom Field Type
• Code: Create a custom field type from scratch

Buy It

• Enterprise Edition: Use the Out of The Box Enterprise Edition functionality
• Buy: Buy a pre-made Custom Field Type

JavaScript

By adding a Content Editor Web Part to each page you want the icon to display on, you can add JavaScript that will insert icons once the page has been rendered.

Christophe at Path to SharePoint uses his signature HTML Calculated Column to do most of the hard work in his article: Apply color coding to your SharePoint lists. In this instance JavaScript is used solely to render the HTML correctly, as SharePoint renders the output of calculated columns as text normally.

Designer

If you don’t mind spending a little time dabbling with SharePoint Designer, and you can convince your Site Administrator you’re probably not going to do anything too damaging; then Microsoft’s free tool may be the solution for you.

Toni Frankola has risked the wrath of Microsoft and written an article on how to use Designer reproduce Enterprise edition’s KPI columns without having to upgrade: Visual Indicators for the Masses: KPIs in WSS.

As with the JavaScript solution, you’ll have to make this change on every page you want to see the icons on.

Download

If you’re and end-user looking for a quick solution, or a developer interested in further developing an existing Custom Field Type, then the IconSet CodePlex project may be of interest to you.

I have enormous respect for those that donate their efforts to the community, such as the developers of this project. Unfortunately open source developers often have a day job and other commitments, so expecting rapid free support from them can be a tall order.

Code

It’s entirely possible to create a Custom Field Type yourself. This is by far the most time-consuming of the options listed on this page, and hence also probably one of the most expensive. However, if you want to avoid some of the initial investment, you could use the IconSet CodePlex project mentioned above as a good starting point (or reference guide).

Fortunately, as the icons are directly rendered onto the page you can avoid the majority of the JavaScript rendering problems I mentioned in How to do list highlighting in SharePoint. If you also avoid [Today] then you can avoid some of the related trouble.

A benefit of all three of the Custom Field Type options is that the results are shown wherever the column is shown in a view, avoiding page-by-page additions.

Enterprise Edition

SharePoint Enterprise edition allows you to add KPI information to your site, along with many other additional features. If you’re working with Enterprise edition then take a look at Mark Miller’s article: KPIs for the Masses.

Since use of this functionality is prolific and directly supported by Microsoft it’s very a good option for those that have this version of SharePoint. Unfortunately the functionality isn’t available to those working with Foundation or Standard edition.

Buy

Many companies don’t have Enterprise edition, and feel that upgrading solely to use the KPI functionality is perhaps not the best use of resources. As a result, the functionality has been reproduced by a great many products (not least our own: SharePoint Highlighter).

Because we have our own product in this area, we’ve created a product comparison to demonstrate the available functionality, and associated cost.