FeedReader Contribution

I recently made some changes to Tim Heuer’s FeedReader to help fulfill some client requirements and made some time to contribute the changes to the CodePlex project for others to use.  We have been happily using it ever since.  Tim’s done a great job providing a tool that fills a gap in SharePoint and I’m happy to help make it better.

Tim, thanks for the opportunity to contribute


SharePoint Deployment Guidelines

Apparently Microsoft and I are on the same schedule.  I’ve had an outstanding task to write some deployment guidelines for my current client and we’ve finally been able to give it a priority where I can focus on it.  I still have some finishing up to do, but along the same lines Microsoft just released a white paper titled Implementing Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 Solutions (find it here).  It doesn’t go into as much detail as I do (or maybe a more correct statement would be it goes into different detail), but it gives a good overview of how the different environments interact and some good info on solutions and content deployment. 

Here’s an excerpt from the Executive Summary:
"This document outlines a methodology for SharePoint team development, customization and content authoring that aims at accelerating implementation and mitigates production risks.

To form the methodology, the document reviews implementation scenarios, tools and development environment."

Definitely worth the read.


Designer Workflow “Unknown Error”

We had to go to Microsoft for this solution so I can’t take credit for it but I wanted to post the info here for others who may run into it.

We have a couple lists that have many columns (70 90, roughly) with various data types.  At least one of the columns has the option set to allow multiple selections, like on a Person/Group column.  There is a workflow attached to the list.  It doesn’t matter what the workflow does, could be updating a column value, sending email, whatever.

At some point the workflow fails to complete and throws an error.  Diving into the workflow tasks for the item  the only error shown is "Unknown Error".  Very helpful.  This error results regardless of how the workflow starts, either manually or automatic.

Before we opened a case with MS I did some work to try to duplicate it.  Creating a large list with many column types worked just fine, regardless of combination.  The only way I could re-create the issue was to use a list template created from a list that was already showing the symptoms.

Once we brought in MS we narrowed the error down to workflow’s created within SharePoint Designer.  That was a good step in the right direction. 

My next MS contact was from the Designer team.  He was unable to duplicate the issue by creating a list from scratch as well, but could duplicate it using the list template I provided.  Below is his solution to get the list back to allowing workflow’s without error.

This may be more of a work-around than a solution, but it gets the job done.  Basically, it involves updating the multi-select column value to itself within the workflow along with whatever else the workflow is doing.  If you have many multi-select columns it may take you a couple tries to find the culprit, or you can just do this to all of them and be sure you got it.  It doesn’t hurt.  Here’s the process assuming you have a People/Group column:

  1. Open the workflow that is having issues and click the Variables button at the bottom.
  2. Click the Add button and give the variable a name and a type of string.
  3. Add the Set Workflow Variable action to the top of your Actions since we need to use that variable in the update action.
  4. Set the workflow variable to the current value of the list column by choosing Current Item as the Source and the list column as the Field
  5. Modify the current update list item action (or add one if you don’t already have one) to include the values you want updated. The order doesn’t seem to matter, so just click the add button.
    1. For the Set this field drop down select the name of the column that has the People and Group type.
    2. For the To this value click the fx button and select Workflow Data.
    3. For the Field select the variable we created earlier and click Ok. Keep clicking ok and eventually click finish. At this point your existing list should work.

Open Question:
How does the list get to this corrupt state in the first place?  It’s not related to the number or type of columns.  If you have any ideas please contact me or leave a comment.


Workflow Issues After WSS SP1

As I mentioned in my previous post on my SP1 issues, my Designer workflows stopped working after the service pack.  Specifically, it would no longer start workflows automatically.

I still don’t have the answer (bad news first), but I got another piece to the puzzle today.  A couple co-workers contacted me after hearing I had issues and they pointed me to a related MSDN Forum post.  As you’ll see, there is a suggestion that the auto workflows work fine as long as you’re not logged in using an admin account.  Which is what I was indeed doing (beat me up later for developing as an admin).

So I signed in as another, non-admin, user and sure enough…the workflows worked!  Finally something you can’t do as an admin but can as a normal user!!  Weird.  Anyway, it’s another piece to the puzzle and gives me a temporary work around.