Archive for the ‘General’ Category

SharePoint Datasheet FAQ

Date:October 5th, 2012 Author: Tags: , ,
Category: General, Training Comments:3 ;

faqSharePoint’s datasheet is a powerful tool and a source of much trouble: This article is a quick summary of the common problems and their solutions, where possible.

Unfortunately there is rather a lot that is not possible; the datasheet is not like any other part of SharePoint, as it’s produced by an entirely different method. As James Love explains:

Customisations to the Data Sheet View are not supported, as this is generated using the Microsoft Office Access Web Datasheet Component, which renders the grid using the same base engine as the data sheet view that Microsoft Access uses.

So for the vast majority of questions, the answer is simply:


This is a list of the common scenarios that are not possible via the datasheet view. Click the numbered links for example questions (and further information):

Can I modify the datasheet using JavaScript/jQuery? [1] [2]

No. The datasheet is not rendered as HTML, so it can’t be edited via JavaScript.

Can I apply Conditional Formatting to the datasheet? [1] [2] [3]

No. The datasheet is not rendered via XSL, so Designer can’t be used to change its rendering.

Can I make my cascading lookup work with the datasheet? [1] [2] [3] [4] [5]

No. Editing Custom Field Types is simply not supported in the datasheet:

In SharePoint Foundation, columns based on custom field types are read-only in Datasheet view.

Can I wrap the datasheet column headings onto a second row? [1] [2]

No. To quote Mr. Hammer: "Can’t touch this."

Can I use the datasheet view with BCS (e.g. External Lists)? [1] [2] [3] [4] [5]

No. The datasheet view is only configured for displaying SharePoint data and sees through the the SharePoint-like veneer provided by BCS.

Can I use the datasheet in Chrome/FireFox/Safari/64-bit IE? [1] [2] [3]

No. The datasheet requires the use of ActiveX controls: These are only only available on 32-bit versions of Internet Explorer.


Surprisingly, there are many problems with the datasheet that can be solved:

Can I add the datasheet to a different page? [1] [2]

Yes. Simply add a List View Web Part to the page, and edit it to display a view on the list that’s set to show the datasheet by default.

Can set the datasheet to only allow editing (not adding/deleting items)? [1] [2]

Yes. Edit the users’ list permissions so that they only have access to Edit and View Items.

Can I fix the error "The selected cells are read only"? [1] [2]

Mostly. Here are three possible causes of this:

  • Multiline rich-text fields: Switch them to plain text to edit
  • Approval is enabled: Disable it
  • Metadata fields: Not supported

So this isn’t a very good "Yes", but at least there are workarounds for most of the problems.

Why can’t I open the datasheet view? [1] [2] [3]

This appears to usually be caused by having 64-bit Office installed on the client machine. It can apparently fixed by installing the 2007 Office System Driver: Data Connectivity Components according to KB 2266203.

Interestingly, if you happen to not have Office at all (because you’re on a server, or writing an article on your home laptop) you may need to install the Microsoft Access 2010 Runtime instead.

Can I completely rewrite the datasheet view? [1]

Apparently yes (see linked question), although I’m not sure you’d want to.

SharePoint Online – options for email enabled document libraries and lists.

Date:August 18th, 2012 Author: Tags: , , ,
Category: General, SharePoint Online / 365 / Cloud Comments:2 ;

“Email enabled document libraries” are a popular feature in SharePoint – you can send email to a specific address and the email gets put into a document library or list.

This feature isn’t supported in the hosted version of SharePoint (SharePoint Online / Office 365 or BPOS) but there are 3rd party apps that enable this.

A SaaS app that allows rules for what happens to the emails based on email address, content, attachments and promote email content to list meta data. Currently in limited beta, pricing not decided.

Runs as an application on a local workstation and moves emails from an Exchange Online mailbox to SharePoint Online list according to user defined rules. Free to use – support provided if you set MessageOps as ‘partner of record’.

SaaS app to to provide email enabled document libraries with options to store attachments away from SharePoint storage. Pricing not disclosed.

Desktop program that runs in the background on a user’s computer and move emails from Outlook 2007/2010 folders into SharePoint online or on-premises. From $165 per profile (folder/incoming email address).

In the Cloud: New web parts for SharePoint Online!

Date:July 23rd, 2012 Author: Tags: , ,
Category: General, SharePoint Alert, SharePoint Online / 365 / Cloud Comments:0 ;

We know that some customers are considering moving to SharePoint Online and have been asked if our SharePoint web parts are compatible.

To run on SharePoint Online a web part has run in the Sandbox Model. Quite frankly this is hard and there are many restrictions – which is why there are so few vendors selling cloud compatible web parts. For our own products some features would have to be removed (e.g. web part connections in Planner and PivotPoint) some would have to be radically re-designed (such as TeamTime) and with some (FilterPoint and Highlighter) it’s just not possible to run them in the sandbox model at all.

The strategy we’re adopting is to create SharePoint Online / Cloud specific versions of our web parts to avoid having to ‘dumb down’ our normal on-premises web parts.

Date based email alerts for SharePoint Online

First up is a cloud specific version of Reminder that allows you to add customizable and date based email alerts to SharePoint Online / Office 365.

Date based email alerts for SharePoint online

Email enabled document libraries in SharePoint Online

We’re also developing a service that will allow you to use Email enabled document libraries in SharePoint Online – something that’s provided out of the box in normal on-premises SharePoint installations and many people are surprised to learn is just not available in SharePoint Online.

Email enabled document libraries for SharePoint online / 365

Not in the cloud?

Don’t worry, our feet are still firmly on the ground! We’re not going to forget about those of you who don’t plan to move to SharePoint Online and those of you who appreciate the extra flexibility of traditional on-premises installations that give more power to be able to adapt and enhance the platform your your needs.

As always – get in touch if you have any questions or feedback or would like to let us know which product you would like us to adapt.

SharePoint Sandbox Solutions: The Good, The Bad, and The Ugly

Date:July 11th, 2012 Author: Tags: , , , ,
Category: General, SharePoint Development, SharePoint webparts, Training Comments:3 ;

Sandbox solutions are often seen as the cure-all for the worries of installing in-house or third party software on your SharePoint farm; but all is not as it seems.

This article aims to dispel some of the illusions around the safety of Sandbox Solutions, and cut through some of the fluff about what the sandbox should actually be used for and why.

  • The Good: What sandbox solutions do well
  • The Bad: What sandbox solutions don’t protect you from
  • The Ugly: The compromises you have to make to use them

What is a Sandbox Solution?

A Sandbox Solution is just like a normal Farm solution, except that it is deployed to a specific Site Collection (rather than the whole Farm), and has a limited set of tools it can use.

A full listing of what you can and can’t do in the sandbox can be found here:

Sandbox Solution Considerations (section “Capabilities and Elements in Sandboxed Solutions”)
Restrictions on Sandboxed Solutions in SharePoint 2010

It’s just like having a toddler in a sandbox in your garden (or yard): They can build sandcastles and dig holes using the tools you give them, but they can’t play with the chainsaw or ride-on mower you’ve left lying around (or dig enormous holes in your flower beds).

The Good

Sandbox Solutions are prevented from doing many things that could cause security or performance issues on your SharePoint server. Notable restrictions include:

  • No access to the network(s) your server is connected to
  • No access to the server’s registry
  • No access to the server’s filesystem
  • No access to e-mail via SMTP
  • Permissions cannot be elevated

There are also some additional features to help keep solutions in line:

  • Solutions can be installed at the Site Collection level by Site Collection administrators.
  • Resource Usage Limits are applied to solutions and can be monitored and limited by the administrator, preventing faulty or processor-hungry code from overwhelming the server.
  • Solutions can be automatically validated, and known troublemakers can be banned from the entire farm.

Notably, the main benefit to the Site Collection administrator is the ability to deploy their own solutions, but the majority of the other benefits are to the Farm administrator (and/or hosting company); although everyone benefits from the improved system stability these features help to ensure.

The Bad

There are a great many features to help with system stability and the prevention of security breaches; but there are limits to what the solutions are prevented from doing.

You should certainly never deploy untested third-party solutions to the sandbox “without fear of bringing down the entire farm”.

The best example of a danger to stability from within the sandbox is the lack of control over the Client Object Model, mentioned here: Sandboxed Solutions in SharePoint 2010

Pages, Web Parts, and controls that are deployed in sandboxed solutions can include code that runs against one of the SharePoint Foundation client-side object models … Code that runs on the client computer is not subject to any of the code execution or resource usage restrictions.

For example, a solution could contain malicious or badly written code executed via COM that requested all the items in a list an infinite number of times. If embedded into a web part, this would effectively turn the computer of every user that viewed it into a node of a DDoS attack on the server farm.

Rather less dramatically, it’s worth noting that there are no specific restrictions on actively malicious code within a Site Collection. It’s perfectly possible to:

  • Delete sites and sub-sites
  • Add COM calls to export data to an external site (much like Wictor’s data import)
  • Copy data added/edited in lists with item-levels permissions to unrestricted lists

The Ugly

Although sandboxing adds restrictions at every level of SharePoint, the feature wasn’t in the original platform design (in SharePoint 2007). In order to squeeze this feature in, some sacrifices had to be made.

Since there’s no access to the filesystem, the following aren’t possible:

  • Application Pages
  • Visual Web Parts (since they deploy a Control Template)

There are a some compromises due to Split Page Rendering; where sandboxed web parts are rendered separately from the rest of the page in a controlled thread:

  • No Script Manager to output/organise JavaScript
  • No web part connections
  • No access to the page Cache

Similar to the above: Because sandbox solution code needs to run in a controlled thread, the following functionality (that uses separate threads) had to be removed:

  • Workflows containing code
  • Timer jobs

Although most of these compromises are understandable, there are some features that are missing for no apparent reason:

  • You cannot use any of SharePoint’s own web controls (e.g. Date picker, User selection)
  • You cannot hide Custom Actions, or add Custom Action Groups


Sandboxing makes it less likely that you’ll accidentally destabilize a SharePoint farm with broken code, and make it easier to find and deal with trouble making solutions.

It’s also more difficult for malicious code to gain access to anything outside the Site Collection it’s deployed to, and slightly more difficult to destabilize the farm.

However, it doesn’t guarantee safety from either bad or malicious code and there are a large number of compromises to consider. Working around sandbox limitations will add overheads to most development projects, and many solutions will simply not fit into the sandbox model.

For example: FilterPoint and Highlighter are two of our own products that can never be made sandboxable, as they’re based on features that are simply not available in the sandbox.

Edit: Since the publishing of this post, we’ve discovered that sandbox solutions are now deprecated in SharePoint 15; as mentioned in the article SharePoint 2013 preview – Apps or Crapps?.

Tip – Keyboard shortcut for Paste As Plain Text in SharePoint

Date:June 14th, 2012 Author: Tags: , ,
Category: General Comments:5 ;

If you spend any amount of time copy and pasting stuff into SharePoint’s wiki or rich text fields (or indeed working with web based rich text editors of any kind) then you’ve undoubtedly have been burned by the crAzY FormaAting monster! This is because the formatting that works so beautifully in one place may not work well in another site.

Of course in SharePoint 2010 you’ve got the Paste as plaintext option in the toolbar, but I am a keyboard warrior damn it! I don’t have time for faffing about with a mouse!

If you’re as impatient as I am (or aren’t using SharePoint 2010) you’ve probably got around this with the Notepad dance to remove formatting – Select source, CTRL+C, Open Notepad, CTRL+V, CTRL+A (select All), CTRL+C, switch to destination and finally CTRL+V to paste plain text… but there is an easier way – CTRL + SHIFT + V to Paste As Plain Text!

If you’re using :-

New version of PivotPoint web part for SharePoint – v2.2.3

Date:May 15th, 2012 Author: Tags: , , ,
Category: General, PivotPoint Web Part Comments:0 ;

A new version of our PivotPoint web part for SharePoint (v2.2.3) is ready.

This new version improves performance for large lists, corrects bugs when you have angled brackets (“<” and “>”) in your row or columns, adds support for site column lookups and a 2 new features.

Sort by Title or Total

The new version of PivotPoint allows you to sort by both the Title and Total rows, either ascending or descending.

Title and Total cells

For example, instead of sorting alphabetically by product you can sort by their total sales – showing your best performing products at the top of the table or left of the chart.

PivotPoint showing all columns

More details are in the online manual.

Show Top N

In combination with sorting by the Total you can choose to show the Top N columns or rows.

For example given the following data the vast majority of revenue comes from 2 products (Bottle-o-matic and Can-o-Matic) and we have a ‘Long Tail’ of other products.

We can choose to only display the top 2 columns (products) and optionally group all the other sales into “Other”

PivotPoint for SharePoint showing top 2 columns

 More details are in the online manual.

You can download and upgrade to the latest version without losing any settings.

10 things developers should know about SharePoint

Date:May 4th, 2012 Author: Tags: , , , ,
Category: Community, General, SharePoint Development, Training Comments:1 ;

Many developers walk into the world of SharePoint unaware of the strange and interesting journey of discovery they’re about to begin.

It’s often difficult to know where to being, so here’s the top 10 most useful things I’ve learned since I joined Pentalogic back in 2010.


1. Know your Editions
2. Don’t even look at the database
3. Get to know the front-end
4. Dispose of your disposables

Building your Knowledge

5. Learn the language
6. Get a good book
7. Love the MSDN documentation
8. Find a SharePoint community that suits you

General advice

9. Learn to live with CAML
10. Remember that SharePoint is enormous

1. Know your Editions

SharePoint comes in many flavours, each of which has it’s own features and shortcomings. Here’s a quick run down of the notable versions:

Release Cheap Expensive MS Hosted
2010 Foundation Standard/Enterprise SharePoint Online
/ Office 365

It’s useful to get to know these for when you’re searching for solutions, as you’ll sometimes come across those that are edition specific (e.g. the Standard Edition’s ContentIterator class for querying large lists).

There are few things more frustrating than finding the perfect solution, and then discovering you have the wrong Edition.

2. Don’t even look at the database

To those new to SharePoint this is entirely baffling: Why wouldn’t you want to get data from the database? There are two good reasons for this:

a) Microsoft is very touchy about their database. They will not support any installation with software on it that modifies the SharePoint database.

b) The structure will give you nightmares. At some point in almost every database developer’s career they say: “Why don’t we abstract the table structure, and just have one massive generic table of text data?”

They’re then hit in the head by whatever small throwable object happened to be nearby, and their colleagues point out that although it would be very flexible, it would also be fantastically slow and unwieldy.

Unfortunately either the SharePoint team operated a clean desk policy, or they put an extraordinary value on flexibility, and the result is lurking in the darkness of the SharePoint database.

3. Get to know the front-end

It’s very tempting to dive straight into the code side of things, but when you’re trying to orientate yourself in the API it helps to have a good understanding of what you’re looking at from the front-end.

It’ll also give you a good feel for the site’s design, and hence what sort of layout the users will expect to see.

Many of the actions you perform in code will correlate to actions in the front-end, as well as the structure.

For example, to find a particular list’s view in the front-end, you would:

  • Open the site using the URL
  • Open the sub site
  • Select the list
  • Select the view

The code version of which is very similar in structure and information needed:

    using (SPSite site = new SPSite(http://site))
         using (SPWeb web = site.OpenWeb("subsite"))
             SPList list = web.Lists["List name"];
             SPView view = list.Views["View name"];

4. Dispose of your disposables

Some SharePoint objects (in particular SPWeb and SPSite) won’t automatically dispose of themselves when they’re no longer used. If you’re unaware of this, then you may easily run into post-deployment problems caused by the ensuing memory leaks.

The code in the previous section shows one method of dealing with this problem, and here is Microsoft’s advice on the subject: Disposing Objects

Interestingly, you shouldn’t always dispose of these objects; for example you shouldn’t dispose of  SPContext.Current.Web. As a general rule of thumb:

If you made it, dispose of it. If you were given it, leave it.

5. Learn the language

There is a huge amount of SharePoint-specific terminology, and some of it can be inconsistent and often misleading. For example, a Site Collection is an SPSite object, but a Site is an SPWeb object.

Another example that caught me off guard at first was that there’s a difference between the Object Model (the server-side SharePoint API) and the Client Object Model (client-side API). Whereas I was under the impression that one was an abbreviated form of the other.

Microsoft has published an enormous glossary, which seems to cover quite a lot of it: Glossary for SharePoint 2010. Although as with any jargon or language, most of it is learned along the way.

6. Get a good book

A good reference guide is infinitely more useful than an enormous glossary when getting to know the components of SharePoint. It’s vitally important that you get an overview of all of these components, to avoid inadvertently reinventing the wheel.

There are two I can personally recommend (having read them both cover-to-cover):

Building the SharePoint User Experience (Furuknap): Written for 2007, but still covers the mainstay of SharePoint. An easy and interesting read: If you’re quickly bored by dry textbooks, then this is definitely the book for you.

Inside Microsoft SharePoint 2010 (Various): A good follow-on from Furuknap’s book. A solid foundation of 2010 knowledge, and a good one to refer to now and again. Don’t start with this book though, or you’ll find yourself climbing a pretty steep cliff.

As your SharePoint knowledge grows, revisiting the books can also be quite useful. Parts you may have glossed over previously will suddenly start to make more sense, and you may find some useful tips you missed first time.

7. Love the MSDN documentation

Having developed and worked with a great many third party APIs and interfaces in the past, I can say with considerable confidence that the MSDN documentation is phenomenal.

Every class, method, and property is documented. Even the most obscure properties have at least a placeholder page, which in itself offers more information than many specifications. On top of this is the community comments on each page add clarification and often links to useful related articles.

However, there are two minor shortcomings. The first is that the background documentation (such as “Disposing Objects” mentioned above) is usually painfully boring to read and often skims around subjects rather than getting to the point.

The second is that the CAML documentation is very bizarrely structured: Elements used for almost completed different things share the same page just because they have the same name. There is also missing documentation where the CAML is more obscure, such as the elements used in SPWeb.ProcessBatchData().

8. Find a SharePoint community that suits you

Sometimes no amount of Googling or searching of MSDN’s documentation will find you the answer to the problem that’s been bugging you. In these circumstances it’s good to have a community of like-minded SharePoint developers to help you with your problem.

Being an active member of a community will also help you to expand your knowledge of SharePoint in general.

Here are a couple of the more notable SharePoint developer-friendly communities:

I’ve previously discussed the differences between the two in the following article: SharePoint Questions: MSDN versus Stack Exchange

9. Learn to live with CAML

Collaborative Application Markup Language (CAML) is another example where flexibility seemed to take precedence over usability. In certain circumstances you’ll be forced to write unserializable and poorly validated XML to perform seemingly simple tasks, such as importing comparatively small quantities of data (a few thousand rows).

However, it isn’t all bad: As I mentioned, CAML does allow a great deal of flexibility, and also has very easily readable syntax. The core resource for CAML can be found here: Collaborative Application Markup Language Core Schemas

When querying data you can avoid CAML by using LINQ, which is reputedly faster and easier to use. If you have no fear of CAML (or are working on 2007), the following tool may be of use to you: U2U CAML Query Builder

P.S. While we’re talking about tools, I should mention the extensive and impressive list of SharePoint development tools found here: List of SharePoint 2007 development tools

10. Remember that SharePoint is enormous

It’s important to bear in mind that SharePoint is a mind bogglingly large framework, with dark corners that even the SharePoint Development Team themselves haven’t visited in years.

This is important because occasionally you’ll find an area that’s poorly documented or has strange known issues, and it helps to have a little perspective on the scale of the system you’re dealing with.

You also need to be aware that there’s an awful lot you don’t know, and some of which you may never know. Getting a good overview of the components is essential. I wouldn’t recommend designing a project to use a component (such as a Custom Field Type or Site Template) until you’ve at least made a prototype in that area; to appreciate the depth of what you’re tackling.

The variety of customizable components in SharePoint also means that there is almost always more than one solution to a problem, as you can see in some of my previous posts: How to do list highlighting in SharePoint


The first challenge in SharePoint is discovering the existence of all the things you don’t understand yet. Once you’ve got a vague idea of all the different components, then you can really start to learn what each is about.

To borrow Mr Rumsfeld’s turn of phrase: Once all your unknown unknowns are known unknowns, you can start learning known knowns.

SPrello – an open source UI for SharePoint 2010 inspired by

Date:February 14th, 2012 Author: Category: General Comments:1 ;

Even with all the fancy project management and collaboration tools available I bet most offices still rely to some extent on the more traditional methods – white boards and post it notes!

Last year Fog Creek Software released very swish app called Trello that aims to move these post-it notes into the 21st century.

“Trello is an online collaboration tool that organizes projects into boards. In one glance, Trello tells you what’s being worked on, who’s working on what, and where something is in a process.”

As we use SharePoint for much of our day to day collaboration (no surprise there) I wondered if a similar interface could be made for SharePoint?

Hence SPrello was born. It’s pretty basic (at the moment) and will likely never have the real time features of Trello but I hope it can be useful and as it’s an open source project you can adapt and build upon it to fit your requirements.

It’s been released as an open source project on Codeplex

  • SharePoint 2010 sandbox web part
  • EMCAScript Client Object Modell
  • JQuery/JQueryUI libraries

If you find it useful please come back here and let us know how you’re using it!

SharePoint Timesheets – What are your options? Part 3: Free Solutions

Date:November 10th, 2011 Author: Tags: , , , ,
Category: General, SharePoint TeamTime, SharePoint Timesheets Comments:6 ;

Following on from Clare’s previous two posts on Native SharePoint Timesheets and Plug-in one, I’ll be running you through the options for creating SharePoint Timesheets for free.

During the early development of SharePoint TeamTime we looked at our potential competition, including the free alternatives. Of those we found, the following three were the most notable:

  • Fab 40 – Timecard Management: One of the famous Fab 40 templates (2007 only)
  • Built-in Timecard List: A little known built-in Timecard list (2010 only)
  • Open Source Project: Paul Beck has kindly published an open source solution (2010 only)

Fab 40 – Timecard Management

The Timecard Management template was produced by Microsoft as a demonstration of the capabilities of WSS 3. In Microsoft’s own words:

The Timecard Management application template helps teams track hours spent working on various projects. The site enables team members to ‘punch in’ on a particular project and ‘punch out’ when they cease work. The system automatically generates the time worked by project, and can show managers who is working on a particular project…

This was one of the favorites out of all the templates we tried. In fact, the punching in and out functionality was a feature we emulated into TeamTime. I’d like to think of TeamTime as a spiritual successor to this template.

Built-in Timecard List

SharePoint 2010 has a built-in Timecard list, that is hidden from normal view for some reason. Although this is by no means a complete solution, it’s freely available to anyone able (or willing) to activate the feature and create it though SharePoint Designer 2010.

Laura Rogers has a very helpful walk-through for creating one of these lists: Out of the Box Timecard and Holiday Lists. Here is a description from her blog:

In SharePoint 2010, there’s a little-known built in feature.  There are list templates that can be used for time card tracking, with a holiday calendar that ties into the time card.

Open Source Project

Paul Beck has published a four part blog series on creating a Timesheet solution from scratch, entitled Timesheet solution for SharePoint 2010. He then went a step further and published his code to CodePlex for anyone to use. In his own words:

A common requirement on Intranets is to have a timesheet template on SharePoint.  There are solution for company timesheets.  I wanted to build a timesheet application that was scalable, reportable and friendly for SharePoint.

If you want to skip the source code, his third article in the series (Part 3 – Installation) has a link to the pre-built package.

This solution is slightly different from the others, as it stores its data in a separate SQL Server database; which may not be an option for everyone.


I hope you’ve found our  SharePoint Timesheet series useful. If you know of any better alternatives, please let us know. We’re not afraid of a bit of competition. Winking smile

SharePoint TimeSheets – What are Your Options? Part 2: Plug-in Commercial Solutions

Date:November 3rd, 2011 Author: Tags: , , ,
Category: General, SharePoint TeamTime, SharePoint Timesheets Comments:0 ;

This is the second part in our series covering the options available for anyone looking to implement a timesheet or time tracking system within SharePoint.

Those of you who are regular readers of this blog will know that we have been doing some work with SharePoint Timesheets recently. As a part of that we have spent quite a bit of time looking at what’s currently available. In the spirit of social sharing we thought we would give you a rundown of what we have found.

I want to stress here that we haven’t tested all of these timesheet applications. We’re not aiming to offer any kind of recommendations here, simply a handy run down of what’s available: A brief summary of each product in the publishers own words, and an idea of pricing where possible.

In part 1 we looked at native commercial SharePoint Timesheet applications.  Today we are looking at Plug-in Commercial SharePoint Timesheet software. In other words Timesheet applications which, whilst not built in SharePoint, can be accessed via your SharePoint site. These applications may offer functionality which is not available within the confines of SharePoint. A potential issue to consider if purchasing in this category would be that of data integration.

TeamTimesheet (AssistMyTeam)

Product Homepage

This is an interesting one.  Time is input in Outlook, and then reported in SharePoint:

Team TimeSheet for Outlook & SharePoint is an enterprise time reporting and billing management solution for team to work, plan and execute project related activities and prepare timesheets in Microsoft Outlook and publish to the company’s SharePoint site.

Pricing starts from $600 for a 10 user license.

TimeControl (HMS Software)

Product Homepage

TimeControl is designed with its own powerful web-based interface. However, for organizations which have adopted the Microsoft SharePoint environment as their Intranet or Corporate Portal software TimeControl can be deployed right inside the SharePoint interface. This allows end users to use TimeControl without ever leaving SharePoint.

Pricing: Although HMS give extensive advice on how to buy the product, they don’t actually provide any indication of the price on their website.

SharePoint Timesheet (Tenrox)

Product Homepage

SharePoint Timesheet is a Web-based timesheet solution offered by Tenrox. This Employee Timesheet and Scheduling Management application leverages SharePoint technology for collaboration, dashboards and reporting. Tenrox Timesheet is an on-demand solution that works with your SharePoint instance on-premises or on-demand thereby enabling collaboration with team members and customers in various locations.

Pricing: Once again we are in Enterprise land, and the website gives no indication of pricing.

That would seem to be about it for commercial plug-ins.  Again, if we have missed any then please do let me know.

In our third and final instalment we will be looking at creating SharePoint Timesheets for free.