One of the requirements I have had to work on lately is reproducing elements of a Domino UI in sharepoint. That happens to include a long list of sites with links at the top providing the ability to view sites starting with a particular letter.
This of course is quite different from the standard SharePoint paging/filtering/grouping, which is based on page numbers and full text values.
The first approach I tried was to add a filter provider web part implementing ITransformableFilterValues as documented by Ton Stegeman - MOSS 2007 Filter webparts part 1 - create your own provider and consumer .
Unfortunately, the out of box list view web part doesn't provide particularly good support for filter providers. Sending the connection from the filter provider fails with the error "AvailableLinks did not implement the GetInitEventArgs method". Setting up the connection the other way works, but is still quite limited. You can't filter on a url field, the filter operator is always equals, and you can only filter on a column that is visible in the current view.
The first two constraints mean that we will need to create an additional column "FirstLetter" that is calculated based on the url title.
The third constraint means that we will need to use query string filters instead of a connected web part. Query string filters do have a few limitations, in particular that they apply to every list on the page. However, this will not be a problem in this case as the page will only contain one list view.
The filter portion is easy enough. In the web part render method, create a series of links in the format
<a href="?FilterField1=FirstLetter&FilterValue1=A">A</a>
AlphabetFilterWebPart.cs Render Method
protected override void Render(HtmlTextWriter writer)
{
try
{
writer.Write(string.Format("<a href=\"?FilterClear=1\">{1}</a> ", "0", "All"));
writer.Write(string.Format("<a href=\"?FilterField1=FirstLetter&FilterValue1={0}\">{1}</a> ", "0", "0-9"));
foreach (char c in "ABCDEFGHIJKLMNOPQRSTUVWXYZ".ToCharArray())
{
writer.Write(string.Format("<a href=\"?FilterField1=FirstLetter&FilterValue1={0}\">{1}</a> ", c, c));
}
}
catch (Exception ex)
{
writer.Write(ex.Message + " " + ex.StackTrace);
}
}
Populating the FirstLetter column is a little more complex. A calculated field would be ideal, but that won't work for a links list as the URL is a complex field type and not supported in a calculated field formula.
The easiest way to handle this is with an event handler. When the link is added or updated, use .net code to update the FirstLetter field.
All the bits not shown are the defaults created by the WSPBuilder templates.
Elements.xml
<?xml version="1.0" encoding="utf-8" ?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<Module Name="WebPartPopulation" Url="_catalogs/wp" RootWebOnly="TRUE">
<File Url="AlphabetFilterWebPart.webpart" Type="GhostableInLibrary">
<Property Name="Group" Value="MyGroup"></Property>
<Property Name="QuickAddGroups" Value="MyGroup" />
</File>
</Module>
<Receivers ListTemplateId="103">
<Receiver>
<Name>AddFirstLetter</Name>
<Type>ItemAdded</Type>
<SequenceNumber>10000</SequenceNumber>
<Assembly>AlphabetFilter, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1f633ef6b7fa5501</Assembly>
<Class>AlphabetFilter.FirstLetterEventHandler</Class>
<Data></Data>
<Filter></Filter>
</Receiver>
<Receiver>
<Name>UpdateFirstLetter</Name>
<Type>ItemUpdated</Type>
<SequenceNumber>10000</SequenceNumber>
<Assembly>AlphabetFilter, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1f633ef6b7fa5501</Assembly>
<Class>AlphabetFilter.FirstLetterEventHandler</Class>
<Data></Data>
<Filter></Filter>
</Receiver>
</Receivers>
</Elements>
FirstLetterEventHandler.cs
using System;
using System.Collections.Generic;
using System.Text;
using Microsoft.SharePoint;
using System.Text.RegularExpressions;
namespace AlphabetFilter
{
public class FirstLetterEventHandler:SPItemEventReceiver
{
private void SetFirstLetter(SPListItem item)
{
if (!item.Fields.ContainsField("URL")) return;
if (!item.Fields.ContainsField("FirstLetter")) return;
SPFieldUrlValue urlvalue = new SPFieldUrlValue(""+item["URL"]);
string firstlettervalue = "" + item["FirstLetter"];
string linktitle = urlvalue.Description;
if (
!string.IsNullOrEmpty(linktitle)
&& (
// no first letter
string.IsNullOrEmpty(firstlettervalue)
// first letter does not match and is not 0
|| (firstlettervalue != "0" && !linktitle.StartsWith(firstlettervalue, StringComparison.InvariantCultureIgnoreCase))
// firstlettervalue == 0 iff title starts with number and first letter is not 0
|| ((firstlettervalue == "0") == (Regex.IsMatch(linktitle, "^([a-z]|[A-Z]).*"))))
)
{
// to simplify the filter web part, the value set will always be
// an uppercase letter or 0 for other characters.
if (Regex.IsMatch(linktitle, "^([a-z]|[A-Z]).*"))
{
item["FirstLetter"] = ("" + linktitle[0]).ToUpper();
}
else
{
item["FirstLetter"] = "0";
}
item.Update();
}
}
public override void ItemAdded(SPItemEventProperties properties)
{
base.ItemAdded(properties);
SetFirstLetter(properties.ListItem);
}
public override void ItemUpdated(SPItemEventProperties properties)
{
base.ItemUpdated(properties);
SetFirstLetter(properties.ListItem);
}
}
}
Once this is working, you will want to remove the FirstLetter field from the form. To do this:
1. Enable content type management on the links list
2. Edit the link content type
3. Edit FirstLetter and set it to hidden so it will not appear on forms.
Another option I looked at was using Ishai's Advanced Content Query web part, as that is already in use on the site and does handle filters properly. However, that would mean replacing the good parts of the out of box list view as well as the bad parts, making it less desirable than the query string filter solution.
If you need to add the paging functionality to another sort of list, filtering on the title column, create FirstLetter as a calculated column with the formula
=IF(ISNUMBER(VALUE(LEFT(Title,1))), "0", LEFT(Title,1))