Posts Tagged ‘SharePoint’

Meet the New Boy–or how to Hire a SharePoint Developer

Date:November 3rd, 2010 Author: Tags:
Category: General Comments:5 ;

Stuart Pegg - smallAfter a long and rather painful summer of searching for a new developer to join our team, this week we are delighted to welcome Stuart Pegg on board.

First let me tell you a bit about the pain.  We knew it wasn’t going to be easy. We wanted someone who was going to be happy to immerse themselves in deep coding.  We made no secret of this.

We knew that tucked away as we are in a a little backwater of rural England we weren’t likely to get an experienced SharePoint developer.  If we could find a really hot ASP.NET/C# developer we were happy to train them up on the SharePoint bit.

But what we found in very long search was that although we did meet a few very good people, an awful lot of the people out there looking for jobs as developers didn’t seem to be able to  – well – didn’t seem to be able to develop really!

It was a bit of a shocker.  We followed the Joel Spolsky approach and set some practical tests at interview – things that we thought were pretty simple, and would be fair on candidates even under interview pressure.

But a surprising amount of people who looked great on paper and talked a really good talk at interview were totally flummoxed by our practical tests – a couple were even downright offended!

So – the learning form this for us is that just because a persons cv/resume is littered with every programming acronym know to man, and just because they tell you at interview that they are a Six Sigma Black Belt Agile Scrum Master, doesn’t mean they can actually write decent code.  Make them write some code at interview. And if they think that’s beneath them, then you probably don’t want them working for you anyway.

Stuart impressed us at interview by being the only candidate to explain his solution to our interview “test” programming problem so clearly that even a technophobe like me could understand it.

Having started on Monday, Stuart has continued to impress us by finishing all the work we had planned for his first week in just 2 days – that means he gets to make all the tea for the rest of the week!

Stuart joins us after spending 4 years working as a developer and manager at Club Communications, providing hosted ordering and billing platforms for the telecoms industry.

When he’s not working he enjoys hill walking and camping, reading and playing computer games,  and weekend visits to family and friends, where he inevitably gets roped into a bit of unpaid computer maintenance.

As he’s new to SharePoint Stuart is still in the honeymoon period of that love/hate relationship we all have with it.  He will be sharing his first impression in these pages over the coming weeks.

So welcome on board Stuart – mine’s tea with 2 sugars please!

Meet the New Boy–or how to Hire a SharePoint Developer

Date:November 3rd, 2010 Author: Tags:
Category: General Comments:5 ;

Stuart Pegg - smallAfter a long and rather painful summer of searching for a new developer to join our team, this week we are delighted to welcome Stuart Pegg on board.

First let me tell you a bit about the pain.  We knew it wasn’t going to be easy. We wanted someone who was going to be happy to immerse themselves in deep coding.  We made no secret of this.

We knew that tucked away as we are in a a little backwater of rural England we weren’t likely to get an experienced SharePoint developer.  If we could find a really hot ASP.NET/C# developer we were happy to train them up on the SharePoint bit.

But what we found in very long search was that although we did meet a few very good people, an awful lot of the people out there looking for jobs as developers didn’t seem to be able to  – well – didn’t seem to be able to develop really!

It was a bit of a shocker.  We followed the Joel Spolsky approach and set some practical tests at interview – things that we thought were pretty simple, and would be fair on candidates even under interview pressure.

But a surprising amount of people who looked great on paper and talked a really good talk at interview were totally flummoxed by our practical tests – a couple were even downright offended!

So – the learning form this for us is that just because a persons cv/resume is littered with every programming acronym know to man, and just because they tell you at interview that they are a Six Sigma Black Belt Agile Scrum Master, doesn’t mean they can actually write decent code.  Make them write some code at interview. And if they think that’s beneath them, then you probably don’t want them working for you anyway.

Stuart impressed us at interview by being the only candidate to explain his solution to our interview “test” programming problem so clearly that even a technophobe like me could understand it.

Having started on Monday, Stuart has continued to impress us by finishing all the work we had planned for his first week in just 2 days – that means he gets to make all the tea for the rest of the week!

Stuart joins us after spending 4 years working as a developer and manager at Club Communications, providing hosted ordering and billing platforms for the telecoms industry.

When he’s not working he enjoys hill walking and camping, reading and playing computer games,  and weekend visits to family and friends, where he inevitably gets roped into a bit of unpaid computer maintenance.

As he’s new to SharePoint Stuart is still in the honeymoon period of that love/hate relationship we all have with it.  He will be sharing his first impression in these pages over the coming weeks.

So welcome on board Stuart – mine’s tea with 2 sugars please!

New SharePoint FilterPoint web part – public beta released

Date:November 1st, 2010 Author: Tags: , , ,
Category: Filter, General, SharePoint webparts Comments:0 ;

FilterPoint SharePoint webpartWell finally, after months of hard work we are delighted to be able to let you know that we have just released our new FilterPoint web part for SharePoint in beta.

FilterPoint has been a long time coming so we hope you are going to like it.  It’s a tool that we always knew we wanted to develop. Dynamic filtering  – the ability to flip between filter values at the click of a mouse – is one of the building blocks for the kinds of rich applications that our customers like to build for themselves.  It builds on the power of webpart connections (a much neglected area in SharePoint) and once you have the ability to apply a group of filters to a page with a selection of webparts and lists you have the potential for some really nice dashboards.

But, as I said FilterPoint has been a long time coming, because what started out looking like a straight forward project turned out to be anything but . . . .

It starts off looking ever so simple with plenty of online examples – but when you start delving into the details it quickly becomes the stereotypical “Can of Worms” project.

There are basically two interfaces you can use – one old IFilterProvider interface , and the new ITransformableFilterValues interface. So far sounds easy but how about some wildcards….

With the new ITransformableFilterValues interface – you can’t create filters dynamically,  and you can’t have multiple connections on the consumer side in SP 2007.

On the other hand, with the old IFilterProvider interface you can’t send multiple filter values to List view web parts and you can’t connect more than one provider web part to a consumer web part. And that’s just scratching the surface.

To top it all off you have little control over what the filter consumer web part actually does with the info you give it – want to say “Equals” or “Not Equals” or “Greater Than” etc and thats out of the scope of what a filter provider can do (we’ve got some ideas on how to work around this in a future version of FilterPoint though).

My oh my, enough to make your head spin!

FilterPoint Webpart, filtering optionsAnyway- we’ve worked really hard to make this web part as simple to use as possible whilst still being compatible with any web parts that can accept the standard web part connections.  We have managed to come up with a tool which allows you to apply multiple filters to multiple webparts and lists, and (at least when working with our Planner and PivotPoint) you can have some control over the operator – using “not equal”, “greater than” and “less than” as well as the standard “equals”.  We hope to extend this aspect of the functionality in v2.

So, why might you want to use this thing then?

Well, you might want to use simply it to guide your users to the most relevant data in one list or webpart – giving them the ability to “filter on the fly”, selecting new data sets, and then clearing filters in one click.

Or, at the other extreme, you might want to bring together a collection of lists and web parts on one page, and use FilterPoint to create a truly dynamic dashboard for your users.

In fact, once you start to use filters and webpart connections there are any number of different ways to enhance the functionality of your SharePoint site with a tool like FilterPoint – we already have it set up on our Sales Pipeline and Client lists here, and are finding more possible uses every day.

We are planning to have FilterPoint ready for full public release by the end of the month.  In the meantime, if you pre-register for your free trial, you will qualify for a 25% discount on the product purchase price.

We hope you like it, and as always, we are keen to hear your thoughts and feedback.

Filterpoint Download

Sharepoint Governance #1 – aim for the sky

Date:October 18th, 2010 Author: Tags: ,
Category: General, SharePoint Ideas Comments:2 ;

So you’ve got your hands on SharePoint and you’re excited. Some might say we’re biased over here at the Pentalogic blog, but we definitely wouldn’t blame you for itching to deploy this user friendly and incredibly powerful server side software across your whole organization super quickly.

But wait a moment! Have you set out who will be in charge of migrating your shared drives to SharePoint, authorising new sites to be created and setting out an information lifecycle to manage your data? What about indexing information so it can be easily searched should you need an answer to be at your fingertips? If any or all of this sounds like a minefield to you, let me assure you that you’re definitely not alone.

Regulating SharePoint affects many users and most of us will look for guidance about managing our use of it at some point. With this in mind, we’ve put together a quick guide to explain why it’s vital to set out protocol for using SharePoint in your organisation sooner rather than later and have added some useful resources for you at the end.

(more…)

Working With SharePoint Wikis

Date:September 23rd, 2010 Author: Tags: ,
Category: General, SharePoint Ideas Comments:1 ;

SharePoint wikis get quite a bit of flack from Wiki enthusiasts – who think they are way too basic and rather a lame example of a wiki.  We disagree:  we quite like SharePoint wiki’s – yes they are very simple and easy to use, but isn’t this kind of the point?  That they should allow you to add and share content quickly and easily?

So we have 2 articles for you here.  This first one is Wiki basics – why and how you would use a SharePoint wiki – and these apply to both SharePoint 2007 and 2010.

And the second installment will take a spin through the new wiki features which are available in SharePoint 2010 – and some of these should be exciting enough to shut up even the most hard core sceptic.

So first up SharePoint Wiki basics.

Why use a Wiki?

Basically a wiki is a bit like a big, on-line, shareable notepad or whiteboard. So if you want your very busy and important subject matter experts to share their pearls of wisdom with the rest of the organization a wiki is probably a great way for them to do that – because its quick and its easy and they can get their point across without having faff around with formatting or worry about where there are going to save the thing. . It’s also really easy for the original author, or others to add, amend and cross reference.  So wikis are also great as team project workspaces, for sharing ideas, gathering information and discussing issues.

You wouldn’t want to use a wiki for structured data (Tasks/Issues/Invoices etc) that would be better in a List and likewise the very unstructured and easy to edit nature of a wiki means that they are probably not the best place for dealing with content that needs a lot of authentication or protection – so for example you might not want your company pay scales, or disciplinary procedures stored in a wiki – as these are things that you want to put a bit of structure around, and that you don’t want every Tina, Deidre and Harriet editing.

Set up your SharePoint Wiki

This is a 30 second job. From the top left of your screen choose Site Actions and then More Options:

From the next screen scroll right the way down to the bottom and choose Wiki Page Library, give it a name, and press the Create button – Job done – you have a Wiki.

Create SharePoint wiki

You can see straight away that the wiki is a friendly and intuitive place to be.  First and best you have the nice big easy to read navigation bread crumbs at the top of the page. Then in the body of the page an introduction to wikis and a link to instructions on how to use them. Finally, a link to your wiki will have appeared on your quick launch menu.

SharePoint wiki home page


So, lets add some Content.

Edit SharePoint Wiki

So as you can see the Wiki page comes with a very Word-like rich text editor, and you can treat adding text to a Wiki page in pretty much the same way as you would add text to a Word document. Just click the Edit link to start and the Save and Close icon when you are finished.

But what are all those square brackets about?

Well, square brackets are how we add a link to a page in a SharePoint wiki library.

Add New Pages

In wikis you are encouraged not to create orphans (pages that are all alone in the world with no links to any other pages) so best practice is first to create a page, then put some content in it.  You created the first page of your wiki library automatically when you created the library.

To create other pages, simply type the name of the page [[surrounded by double square brackets]]

Click “Save and Close” and your pages are created.

Once you’re out of Edit mode – after clicking “Save and Close” you will see that your square brackets have vanished, and you are left with links.  The headings with dotted underlining are for pages with no content yet.  The normal looking links are pages which have content.  So in this example our Planner Demos page has content, but the others have yet to be created.

Sharepoint wiki with links

Just click on one of the dotted links to go to a new page a create content.

This system of page creation is also a great method of getting people started, and keeping them on track with minimal effort.  We all know how getting started is the biggest challenge in any writing project – and keeping on trakc the next.  So say you wanted your subject matter experts to create a wiki on environmental awareness at work you might create pages titled something like:  “recycling”, “power saving”, “car sharing” which might help to steer your environmental experts in the right direction, and stop them wastings hours on things you didn’t want like “windfarms”, “biofuel” and “international environmental policy”.

Add other Links

Using our square brackets we can add different links.

Linking to an existing page is just the same as creating a new page – just enter the page name, surrounded by square brackets:

[[existing page name]]

no need to fiddle around with addresses and / forward slashes.  Wiki pages are not arranged in a “tree” like traditional website pages – it’s all much more laid back and informal (they come from Hawaii remember?).  So just type the name of any page within your wiki and the wiki will find it for you and create the link.  The wiki won’t allow you to create duplicate pages with the same name, try and do that and it will simply link you back to your existing page.

and to link to an external webpage:

[[http://www.yourpage.com]]

To display a link where the link text is different to the destination page name use the pipe character | . So if we wanted to link to the Planner Demos page, but wanted our link to be called “latest demo”:

[[Planner Demos|latest demo]]

Check Revisions and Revert to Previous Version

Need to see who added that really dumb comment? No problem:

SharePoint Wiki Revision HistoryOh . . . looks like that was me!

To get to the revision history choose Page/View All Pages, then click on the arrow next to the page you want to see and choose Version History.  You can see exactly how and when the wiki page changed and who has made the changes.  You can then choose to delete a version, or revert back to an previous version if you wish.

So that’s the basics of working with wikis.

Do you have any other tips and tricks to share?

Next time:  What’s new in SharePoint 2010 wikis.

SharePoint and Visual Studio 2010 – Adding ClassResources to a Web Part

Date:September 20th, 2010 Author: Tags: , ,
Category: SharePoint Development Comments:3 ;

I’ve been working on moving all our products over to Visual Studio 2010. Whilst Microsoft still has some way to go to make SharePoint totally developer friendly (I mean 47 1/2 steps to install SharePoint 2010 on a Windows 7 desktop for development? And shake a double 6 to start? Really?) they have made huge advances and the SharePoint tools built into Visual Studio 2010 are a big improvement on hand crafting or using VSeWSS or WSPBuilder.

I’ve learnt a few things along the way and thought I would pass them on. Today its :-

How to add ClassResources to a Web Part

ClassResources are intended to be used for browser requested resources used in a web part – e.g. images, css files and javascript. This location is often forgotten about and instead these types of files end up spread all over the place.

(more…)

Why Tooltips are cool tips in PivotPoint Webpart for SharePoint

Date:September 9th, 2010 Author: Tags: , , ,
Category: PivotPoint Web Part, SharePoint webparts Comments:0 ;

Tooltips  – those little boxes that pop up when you hover over something – can be a blessing or a bit of a nightmare.  It drives me nuts when people enable those snapshot tooltips on every hyperlink on a page.  the resulting pop ups are huge, usually contain info I don’t want to see, and seem to hang around on the screen for ever.

But imagine a tooltip where you choose exactly what information is displayed?  How cool would that be?  Well that’s exactly what you get with tooltips in our PivotPoint web part  for SharePoint – which is why I think they rock.

(more…)

SharePoint Case Study – Websense Pivot Through Their Marketing Dashboards

Date:September 6th, 2010 Author: Tags: , ,
Category: General, PivotPoint Web Part, SharePoint webparts Comments:0 ;

Hi everyone.

We wanted to share this new SharePoint case study with you.  It shows how online security specialists Websense are using our PivotPoint webapart to slice and dice their marketing list data, and create some awesome, dynamic dashboards.

(more…)

Using [Today] in SharePoint calculated default values

Date:September 2nd, 2010 Author: Tags: , , ,
Category: Calculated Columns Comments:16 ;

Despite the infamous “fake today column trick” still appearing in new blog posts on a monthly basis you can’t use Today in calculated columns in SharePoint.

I’ve seen people assume (not unreasonably) that the same rule must apply with calculated default values used in columns that are not calculated columns as well – but strangely,  you actually can use Today in calculated default values, so I am going to explain why it works and how you might use this.

What is the difference between Calculated Column and Calculated Default value?

A calculated column, erm… calculates values from other columns in your list.

SharePoint - add Calculated Column field

For example if you have an orders list with a Quantity and Price column you can calculate a Grand Total of Price * Quantity.

With a calculated default value you use a calculation to set the default value for a column that is not a calculated column – this is the value that is entered automatically when a new list item is created and may be over-written by the user.

SharePoint - setting a calculated default value

So why may I want a calculation using Today as the default value?

Suppose we have a list containing customer complaints and we have a target to resolve everything in 3 days. Sometimes though for complex queries or if there are public holidays we may give more time. In that case we can set the default value as

= Today + 3

But the user can override that if necessary (public holiday etc).

So why can I use Today here but not in calculated columns?

With a calculated column the calculation is only reworked every time a record is updated. When it’s just viewed then it picks up the saved result from the last edit. This makes perfect sense for most calculated values, but not for values using Today or Me.

So for example if we tried to calculate the days left until a due date we might want to use

Days left = Due Date - Today

If we added the complaint on Monday then it would show that we have 3 days left to do it (Thursday). If we just look at the record on the Wednesday it would still show 3 days (as this was the calculation saved on Monday) when in fact we only have 1 day left to keep the customer happy.

That’s why SharePoint wont let you use Today in calculated columns.

However with a default calculated value the result is only worked out once when the record is being created – it’s understood that what is saved in this field is not updated automatically so there is no problem with using Today.

For a bonus point – you can’t reference other fields in calculations for default values (e.g. Start Date or Order Date) as before a record is being created the fields don’t yet contain values.

What else could I do with this?

The OP in this thread is using it to set default financial years. Suppose that your company’s financial year starts in April then you could use this formula to default to 2009/10 or 2010/11 on or after April.

=IF(MONTH(Today)>=4,"2010/11","2009/11")

or generating the year 20xx/xx notation automatically :-

=IF(MONTH(Today)>=4,YEAR(Today) & "/" & (YEAR(Today)+1),(Year(Today)-1) & "/" & YEAR(Today))

It’s also worth noting that you can use a similar formula in calculated columns – suppose you have an Order Date field and the financial year depends upon when the order was placed then simply replace Today with Order Date.

NB – This has been tested with SharePoint 2007/2010.

Free SharePoint Calculated Column Cheat Sheet
a handy 3 page reference for calculated column functions and formulas.

SharePoint Planner Webpart – new version released

Date:September 1st, 2010 Author: Tags: , ,
Category: General, SharePoint Planner, SharePoint webparts Comments:0 ;

Just a quick note to let you all know that we have just released a new version of SharePoint Planner web part – v2.6.4.

The new version includes a couple of handy new features that might be useful for you.

The new Split Multiple Values option will be useful in resource planning in circumstances where you want to enter multiple category values into one list item, but still view each individual category’s activity as a separate line in your Planner view.  For example you might want to create a list item for a project meeting, with several people in attendance.  In a Gantt view of project tasks it would be appropriate to show this meeting as one item.

sharepoint planner gantt chart

But in a category view of staff availability/commitments you would want the meeting to appear as a separate item for each staff member involved. (more…)