Patch for SharePoint Workflow Time-based Activities

Today I’ve been working on a “Early Warning” workflow designed with SharePoint Designer. It is supposed to run on every item change and to suspend itself until few days before item’s expiry date (it’s just a date column). But, it didn’t work as expected.

I remembered reading that there are some glitches in the way Workflow Foundation dehydrates and rehydrates the “sleeping” workflows. There is a patch available at http://www.microsoft.com/downloads/details.aspx?FamilyID=6096ce0f-d21e-47ac-afe2-d4e1c2fce670&displaylang=en.

I downloaded it and it worked like a charm!

Community Kit for SharePoint 2.0 Pre-Release

Exciting news! The CKS 2.0 has been pre-released. It’s just been a few months since the project started and we already have something tangible.

The features included in this pre-release are:

Enhanced Blog Edition Beta 1
Enhanced Wiki Edition Alpha
ChatterBox AJAX Beta
Tag Cloud

Download any of the components above and play with them (not in production environment, though)…and, above all, provide feedback to the team.

Full announcement can be found here.

Community Kit for SharePoint


Few months ago I joined Community Kit for SharePoint team. It’s a collaborative open-source effort to extend and adapt SharePoint for different communities. This project is led by Lawrence Liu, Senior Technical Product Manager and Community Lead at Microsoft (his blog runs on SharePoint). It’s hosted on CodePlex, at http://www.codeplex.com/CKS.

Right now there are different editions in progress:

I’m collaborating in Corporate Intranet and Internet/Extranet edition as a developer. I’ll publish news from this project on a regular basis.

Stay tuned for much more free releases from CKS project very soon. If you would like to contribute, please visit the project page and see where you can help.

How to Optimize SharePoint Designer’s Use of Content Types in a Workflow

I’m annoyed by many little details of the SharePoint Designer Workflow editor, but the main one is that it profligates in the creation of content types. It creates one content type for any custom form that you create when collecting data from a task. Moreover, it doesn’t give you the chance to reuse an existing type….every new task is a new content type in the Tasks list.

However, you CAN reuse existing content type for the Tasks list. You just have to create the first form as usual and then create a second form with a easy-to-find name such as “DUMMY”. Then, a little bit of manual work follows:

  • Open the XOML file of your workflow with right click, choosing “Open With” then “SharePoint Designer (Open As XML)
  • Find the first “CollectDataTask” action, such as this one

    <ns0:CollectDataTask x:Name=”ID15″ ContentTypeId=”0x01080100AC1C1A96057F4B4897ED6C99E92728F500A85399B392A23943B207F10B3F8BB318″ TaskId=”{ActivityBind ROOT,Path=taskAM}” Title=”CAF Approval 1″ InProperties=”{x:Null}” __Context=”{ActivityBind ROOT,Path=__context}” OutProperties=”{x:Null}” AssignedTo=”{ActivityBind ROOT,Path=userAM}” />

  • Copy the line after the x:Name field
  • Find the CollectDataTask with the Title=”DUMMY”
  • Replace the content of the line after the Name field with the first action copied data

That’s it! Now you can safely remove the DUMMY content type from the Task list and Site Content Types list.

SharePoint Hotfix is available

Microsoft released, at least, a quick-and-dirty hotfix that fixes up several issues with SharePoint Services 3.0.

In particular, I’ve found one of the issues to be very annoying. Namely, when you create a site and customize a list view to something other that the default view and then save the site as a template, these changes are not saved. So, when you create another site based on this template, the list view you customized reverts to the default view.

Among other issues, this is solved in the Hotfix that can be found on this address: http://support.microsoft.com/default.aspx?scid=kb;EN-US;934790

Well…now we have to wait for the SP1 to become available…..I hope it will be this year.

COM Again (0x81020037)

I found this “descriptive” error message in a fragment of MOSS 2007 code in a webpart that uploads and tags a document with appropriate metadata:

Microsoft.SharePoint.SPException: DOMAINuser has modified the file Sample.doc
System.Runtime.InteropServices.COMException (0x81020037)

The code 0x81020037 is “Save Conflict” error code in COM. The culprit:

SPListItem doc = list.Add();
doc[“Field1”] = “Value”;
doc[“Field2”] = “Value”;
doc.CheckIn(“Check-in Message”);
doc.Update(); <-- this is the line that throws the error I tried reversing CheckIn and Update methods, with no success. However, the following trick did the job: SPListItem doc = list.Add();
doc[“Field1”] = “Value”;
doc[“Field2”] = “Value”;
doc.CheckIn(“Check-in Message”);
doc = FindByTitle(doc.Title)
doc.Update();

FindByTitle is a custom method I wrote that finds a SPListItem in a SPList, performing a search on the Title field.

The explication: the underlying COM scaffolding doesn’t like the Update() method after CheckIn(). I had to “reacquire” the item and perform the Update() on this new reference to the same document.

Elementary, dear Watson….

Authentication when consuming a web service with Integrated Authentication

The most convenient way is to pass the user credentials from the client to the web service, providing a DefaultCredential object to the Credentials property of the web service proxy:

ws.Credentials = System.Net.CredentialCache.DefaultCredentials;

before invoking the web service.

How to Serialize a Collection

In a fragment of a code I’m working on, I must serialize a collection of links into an XML file. Fortunately, .NET Framework provides a quick XmlSerializer class to do the dirty job for you.

Well, almost…

The problem

If you try to serialize a class derived from CollectionBase, the Serialize method will throw a nasty exception.

The workaround

Use a container class, put the CollectionBase-derived class as a property, decorate this property with XmlArray and XmlArrayItem tags.

[Serializable]

public class CollectionContainer

{

private LinkCollection _links= new ColeccionEnlaces();

[XmlArray(“Links”)]

[XmlArrayItem(“Link”,typeof(Link))]

public LinkCollection Links

{

get

{

return _links;

}

set

{

_links = value;

}

}

}

Data Caching in SharePoint 2003

If you are used to the ASP.NET Cache object, you can use it in SharePoint (after all, it’s just an ASP.NET extended application). However, the Web part framework encapsulates this Cache and enables you to have per-webpart and per-user cache. How? After a little bit of investigation I’ve found it out. The reason was to find out how to remove a cached item outside the webpart.

After inserting a key/value pair using SharePoint’s PartCacheWrite method, SharePoint creates an entry in the Application Cache object (remember that the cache is shared among all the users), with a custom prefix attached to your own key. This prefix includes:

  • SharePoint webpart key:
    • Request URL
    • Creation date and time of the containing WebPartPage
    • Webpart UniqueID
  • User Security Identifier (SID) in hexadecimal format
  • “?” character which marks the end of SharePoint prefix
  • Your own key

 

So, let’s say you’ve cached an object within a webpart named “_ctl6” (default names for no-name webparts) with a key of “abc” and that the webpart is placed under the URL “/C7/Informatica/default.aspx”. The real cache key is:

/C7/Informatica/default.aspx09/27/2006 11:49:49_ctl60x01050000000000051500000069CE0AC3F42CDE9F7071B56E87080000?abc

It can be broken into the key components:

/C7/Informatica/default.aspx09/27/2006 11:49:49_ctl60x01050000000000051500000069CE0AC3F42CDE9F7071B56E87080000?abc

is composed of:

  • /C7/Informatica/default.aspx
    (Request URL)
  • 09/27/2006 11:49:49 (Creation date of the URL page in SharePoint server time)
  • _ctl6
    (UniqueID of the webpart)
  • 0x01050000000000051500000069CE0AC3F42CDE9F7071B56E87080000
    (User SID in hex format)
  • ? (separating character)
  • abc
    (your custom key)

     

It also inserts two dependency strings, used to invalidate per-webpart or per-user cached data. The names of those keys are Depend_String and Depend_String_Per_User, followed by a SharePoint webpart key:

Depend_String_Per_User/C7/Informatica/default.aspx09/27/2006 11:49:49_ctl7

 

 

Shed some light into SharePoint web part errors

Seeing many of those “descriptive” SharePoint errors like this one lately:

Error
The “MyWebPart” Web Part appears to be causing a problem.
Web Parts Maintenance Page: Use this page to temporarily disable Web Parts or remove personal settings.
Troubleshoot issues with Windows SharePoint Services.

If you want to see more meaningful error description, do a simple trick. Change the following line in your SharePoint web.config into something like this:

<SafeMode MaxControls=”50″ CallStack=”true”>

Of course, make sure NOT to change this switch in your production environment, as it could reveal potentially sensitive information.