SharePoint Dragons

Nikander & Margriet on SharePoint

Tag Archives: best practices

Architecture document for SharePoint

Nice blueprint for approaching an architecture document for SharePoint can be found at: We actually found that the TOC provides a nice comparison with what you might have already.

SharePoint 2010: Best Practices

This Wiki page contains an overview of SharePoint 2010 Best Practices:

What is the SharePoint 2010 best practice: Asset or a Picture library

If you (or your customers) were wondering whether you should use an asset or a picture library, check out our Wiki page at:

Determine the current user in a SPS 2010 workflow

What to do when you want to determine the current user in a workflow? It’s possible that the workflow runs inside the w3wp.exe worker process, in which case the current user makes sense. But it’s also possible that a workflow runs inside the owstimer.exe process, at a later time. In these cases, the current user doesn’t make sense. Instead, use the workflow originator or initiator.

To get the e-mail adress of the originator user:




To get the display name of the originator user:




To get the login name (format [domain name]\[user name]:


These techniques can be used in workflows that are created programmatically. In a SPD (no-code) workflow, you can also retrieve the workflow initiator’s e-mail address: use the User Profile web service as a data form web part in the .aspx page of the workflow to get the e-mail address whenever the initiator started the workflow.

For ongoing work regarding workflow current user retrieval best practices, see: Thanks to for the info.

What to do with historical data in custom lists?

  • If the historical data doesn’t take up much space, leave it in the original list.
  • Turn on versioning if you want to track the history of individual list items.
  • If the history involves different records, leave them in the list and sort the view on the date of the history with the most recent at the top.

Finally, the most common option: eventually archive the items to a different site collection in a different content database.

Follow the ongoing Wiki effort to discuss the best practices regarding this topic at:

Managing SharePoint 2010 log files

A nice link that discusses dealing with SharePoint 2010 database transaction log files: