Aug 31, 2008

The Most Powerfull Activity On Earth - The PowerActivity 1.1

Release 1.1 of the PowerActivity for SharePoint Designer is now available.

  • Even faster...
  • Better logging: now error messages will be added to the workflow's history log, stack traces to the event log
  • Syntax for setting the output has changed
        • from: @{"output"="some value"}
        • to: $output = "some value or variable"
  • No error, no fix :-)

Read more: The Most Powerfull Activity On Earth - The PowerActivity

Hint: Use "get-variable > C:\variables.txt" to print out all available PS Variables to the file system.



Aug 22, 2008

First German Nintex Partner: Data One

I'm pleased to announce that Data One is the first German Nintex Partner.

Nintex is a leading innovator of exciting software products that extend Microsoft technology. They are focused on building software which bridges the gap between what can be purchased from Microsoft today and common functionality requested by customers.

Nintex Workflow 2007
Extends Microsoft SharePoint 2007 and Windows SharePoint Services 3.0 to provide advanced workflow capabilities via a graphical web based interface embedded within SharePoint.

Nintex Reporting 2008
Monitor, audit, and gain valuable insight from the content and activity information within Microsoft SharePoint.

Nintex Podcast Server 2008
Provides organisations with a centralised, easy to use solution to create, manage and distribute Podcasts. Built on Microsoft SharePoint 2007 technology, Nintex Podcast Server enables users to create Podcasts online via an easy to use interface.

Really cool stuff...

Aug 16, 2008

Back and Forth - Lookup Field with Picker and Lookup

I've added two PowerShell Scripts (ConvertLookupFieldWithPickerToLookup.ps1,ConvertLookupToLookupFieldWithPicker.ps1) to my Lookup Field with Picker Release. With this scripts you can convert an built-in SharePoint Lookup to my Lookup Field with Picker and the reverse way my Lookup Field with Picker to an built-in Lookup. Means you can extend an already existing solution with my lookup with picker. On the other hand, if you don't like my lookup with picker (hard to believe;-), just convert back to the boring built-in lookup. Maybe useful for an upgrade to Office 14 - who knows?

  • Convert Lookup to Lookup Field with Picker:

PS>& .\ConvertLookupFieldWithPickerToLookup.ps1 http://[server:port]/site/subsite [ListName] [FieldTitle]

  • Convert Lookup Field with Picker to Lookup

PS>& .\ConvertLookupFieldWithPickerToLookup.ps1 http://[server:port]/site/subsite [ListName] [FieldTitle]

At the moment the script supports only list fields, no contet type fields. Do you need it? Let me know...



Aug 15, 2008

Add the SharePoint List Item's Context Menu to any Column with PowerShell

With this PowerShell script you can add the list item's context menu to any column you want. You'll find the script (AddMenuColumn.ps1) on my Codeplex Project iLoveSharePoint.

I'll just give you an example how to use:

  • Let's assume you have a calculated list column called "justAnyColumn" with the following formula "[Title]&[Content Type]"


  • In this scenario we assume you don't need the title column, instead you want to show the "justAnyColumn" to select an entry. But unfortunately the context menu is attached to the title column. And now?!


  • We could show the "Edit (link to edit item)" column in the view.image
  • May be a solution - But our users are accustomed to use the context menu. Well!
  • Now you can use my script:
  • Start the PowerShell
  • Run my script as follows:
  • PS> & .\AddMenuColumn.ps1 -webUrl http://[server:port]/site/subsite/ -listName "Test" -fieldTitle "justAnyColumn" -addToDefaultView $true
  • Let's take a look at the result:


  • Now you've got a new column, containing the value of "justAnyColumn" with attached context menu.
  • That's all!

How to remove the column?

  • Because the column is read only in the UI, you can't delete there.
  • Instead use my iLovePowerShell script:
    • PS> $web = get-spweb http://[server:port]/site/subsite/
    • PS> $list = $web.Lists["Test"]
    • PS> $field = $list.Fields["justAnyColumn"]; #better would be to use the Guid of the field, because the field name exists twice
    • PS> $field.ReadOnyField = $false
    • PS> $field.Update()
    • PS> $field.Delete()
    • PS> $web.Dispose()

Hope somebody can use this...