SharePoint Dragons

Nikander & Margriet on SharePoint

Monthly Archives: April 2012

Looking for a sneaky way to prevent email notifications from being sent? provides the answer: just change the outgoing SMTP server to something else and switch it back 10-15 mins. Gotta love the simplicity of the idea.

So your mom threw away your Active Directory User…

What happens if a person leaves your organization and, as a consequence of that, somebody throws away the Active Directory user account, only to found out later that it still lingers on in SharePoint? You won’t be able to recreate the user because it’ll have a different SID, so what to do?

Use ol’ stsadm to the rescue: It allows you to migrate a user account to a new login name, optionally ignoring the SID meta data history.

Batch check in

A regular question that pops up is: how do I do a batch check in in SPS and SPF 2010? Not possible ootb, but there’s a 3rd party solution for it called Batch Metadata Edit and Check In:

Websites Like

Jeffrey Carter of Yahoo asked us if we’d like to review a new web site called It helps to find similar, related or alternative websites. We’ve taken a look and weren’t thrilled with the results. We couldn’t find our own web sites and names (we call this the intake test: every time a company is considering to hire you, they will search using your name and it’s best that they find something positive real soon) and when we looked for information about SharePoint we had to wade thru large numbers of commercial offererings without finding quality information. In case you want to check it out, here’s the address: .

Tool for detecting dangerous web sites

A tip by Mark Miller of End Users SharePoint (thanks btw): the web site is a free service that allows users to scan a given website address to determine whether it’s potentially dangerous. To determine this, it uses various virus scanning tools. So, if you’d go to you’ll find we’re safe:


Adding jQuery to a visual web part and then implement parent/child radio buttons

In this blog post we’ll discuss how to use jQuery in a visual web part to help implementing parent/child radio buttons. To accomplish this, we’ve borrowed ideas from other places, we’ll mention them as we go along.

First, create a new SharePoint project and add a visual web part to it. Then, download the latest version of the jQuery library. We’ll be using jquery-1.7.js.

Please note: This is the developer version, which we’ll be using throughout this example. In a production environment, you should use the minified version instead (called jquery-1.7.min.js, or the equivalent of the version you are using).

SPS 2010 contains a new type of library called Site Assets. It can be used to store resource files such as images, style sheets, and JavaScript files. We’ll use it as a new home for jquery-1.7.js. Later, we’ll discuss how to do this automatically, but the next procedure explains how to add the jQuery library manually:

  1. Open a site collection SharePoint Designer 2010 (SPD).
  2. Click the Site Assets node.
  3. Open Windows explorer and browse to jquery-1.7.js.
  4. Drag and drop it within the Site Assets node.

Since we’ve made the jQuery library available within SharePoint, we’ll be able to leverage it. We’ll do this by adding a link to it in our user control (*.ascx), like so:

<SharePoint:ScriptLink ID=”ScriptLink1″ runat=”server”

Name=”~sitecollection/SiteAssets/jquery-1.7.js” />

Please note: You shouldn’t use the ondemand=true attribute, as we want the jQuery library to be available right away.

To test if this has worked, we’re borrowing some ideas from :

  1. Press F5 to open MSIE (we’re assuming you’ll be able to add the visual web part to the web part page).
  2. Press F12 to bring up “Developer Tools”  (for MSIE 8 and higher).
  3. Click the Script tab and verify jQuery is getting loaded. You know this to be true if you find this entry:

    document.write(‘<script src=”/siteassets/jquery-1.7.js”></’ + ‘script>’);

  4. In the right console window, add the following jQuery command:


  5. Click the Run Script button.

If the page background turns cyan, you’ll know that it works and that jQuery did it for you.


At this point, jQuery can be used for client-side scripting.  At this point, the code of the user control of the visual web part looks like this:
<%@ Assembly

Name=”$SharePoint.Project.AssemblyFullName$” %>
<%@ Assembly Name=”Microsoft.Web.CommandUI, Version=, Culture=neutral,

PublicKeyToken=71e9bce111e9429c” %>
<%@ Register TagPrefix=”SharePoint” Namespace=”Microsoft.SharePoint.WebControls”
    Assembly=”Microsoft.SharePoint, Version=, Culture=neutral,

PublicKeyToken=71e9bce111e9429c” %>
<%@ Register TagPrefix=”Utilities” Namespace=”Microsoft.SharePoint.Utilities”

Assembly=”Microsoft.SharePoint, Version=, Culture=neutral,

PublicKeyToken=71e9bce111e9429c” %>
<%@ Register TagPrefix=”asp” Namespace=”System.Web.UI”

Assembly=”System.Web.Extensions, Version=, Culture=neutral,

PublicKeyToken=31bf3856ad364e35″ %>
<%@ Import Namespace=”Microsoft.SharePoint” %>
<%@ Register TagPrefix=”WebPartPages”

    Assembly=”Microsoft.SharePoint, Version=, Culture=neutral,

PublicKeyToken=71e9bce111e9429c” %>
<%@ Control Language=”C#” AutoEventWireup=”true”

    Inherits=”VisualWebPartProject1.VisualWebPart1.VisualWebPart1UserControl” %>
<asp:Label ID=”Label1″ runat=”server” Text=”Label”></asp:Label>
<SharePoint:ScriptLink ID=”ScriptLink1″ runat=”server”

Name=”~sitecollection/SiteAssets/jquery-1.7.js” />

It only contains a reference to the jQuery library. Now, add the code to it that creates a parent/child radio button list. This idea was taken from: and it looks like this:

    $(function () {

        //init Texas
        $(‘#DivTexas :input’).attr(‘checked’, false);
        $(‘#DivTexas :input’).attr(‘disabled’, true);

        //init Virginia
        $(‘#DivVirginia :input’).attr(‘checked’, false);
        $(‘#DivVirginia :input’).attr(‘disabled’, true);

    function EnableTexas() {
        //disable Virginia options
        $(‘#DivVirginia :input’).attr(‘checked’, false);
        $(‘#DivVirginia :input’).attr(‘disabled’, true);

        //enable Texas options
        $(‘#DivTexas :input’).removeAttr(‘disabled’);

    function EnableVirginia() {
        //disable Texas options
        $(‘#DivTexas :input’).attr(‘checked’, false);
        $(‘#DivTexas :input’).attr(‘disabled’, true);

        //enable Virginia options
        $(‘#DivVirginia :input’).removeAttr(‘disabled’);

<asp:RadioButton Value=”A” Text=”A” runat=”server” GroupName=”ParentGroup” ID=”parent1″ onclick=”EnableTexas()” />
<div id=”DivTexas”>
    <asp:RadioButton Value=”AA” Text=”AA” runat=”server” GroupName=”ChildGroupA” ID=”child1″ /><br />
    <asp:RadioButton Value=”AB” Text=”AB” runat=”server” GroupName=”ChildGroupA” ID=”child2″ /><br />
<asp:RadioButton Value=”B” Text=”B” runat=”server” GroupName=”ParentGroup” ID=”parent2″ onclick=”EnableVirginia()” />
<div id=”DivVirginia”>
    <asp:RadioButton Value=”BA” Text=”BA” runat=”server” GroupName=”ChildGroupB” ID=”child3″ /><br />


The result is that you can only check a child radio button if the parent radio button is checked. It looks like this:


Since we don’t want to add the jQuery library manually once we start deploying it, we’re taking an idea from—sharepoint-sandbox.aspx We’ll add the jQuery library as a module to our SharePoint project, and deploy it to a subfolder in the Site Assets library.

  1. Right-click SharePoint project and choose Add > New Item.
  2. Choose Module and call it MyAssets.
  3. Within the MyAssets folder, delete Sample.txt.
  4. Right-click the MyAssets folder and choose Add.
  5. Locate jquery-1.7.js (or better yet: locate the minified version) and add jquery-1.7.js.
  6. Open up Elements.xml, and add the following attribute: Url=”SiteAssets” to the Module element.

Now, the Module XML should look like this:

<?xml version=”1.0″ encoding=”utf-8″?>
<Elements xmlns=””>
  <Module Name=”MyAssets” Url=”SiteAssets”>
  <File Path=”MyAssets\jquery-1.7.js” Url=”MyAssets/jquery-1.7.js” />

Pressing F5 causes jquery-1.7.js to be deployed to the Site Assets library, in the My Assets folder. This means you should update the link in the user control like so:

<SharePoint:ScriptLink ID=”ScriptLink1″ runat=”server”

Name=”~sitecollection/SiteAssets/MyAssets/jquery-1.7.js” />

And there you have it!

Difference between a link and a title

Sometimes you come across a useful piece of information, only to find out that it was provided by ourselves: Still find it useful to share.

Anyways, the difference between a Title and title (linked to item) column is none. They are the same in SharePoint 2010. In SharePoint 2007, there was a difference. After clicking a value in a lookup column with a Title column and then click close, you would return to the target list. If you would click a value in a lookup column with a title (linked to item) column and then click close, you would return to the source list.

Display specific date format in column

Accessing a WCF service that is SharePoint context aware using the WCF channel factory

As discussed in forum thread , this is in fact an elegant way to reference a WCF service in the context of a given SharePoint web site without needing to change the web.config file of the SharePoint web application (this minimizing the overhead of managing custom software):

//Access WCF service Centre Detail Endpoint

WSHttpBinding binding = new WSHttpBinding();

EndpointAddress address = new EndpointAddress(SPContext.Current.Web.Url + “/_vti_bin/MyService/MyService.svc”);

ChannelFactory<IService> factory = new ChannelFactory<IService>(binding, address); IGetCentreNames client = factory.CreateChannel();

Keep relational data in a database or migrate it into a custom list

It’s an interesting question: should you keep relational data in a database or migrate it into a custom list? We’d love our readers to contribute to the discussion at the TechNet Wiki page at

The discussion as it stands so far:

If you need relational database capabilities (transactionality, triggers, real constraints (not the approximation of that in SharePoint)): use the existing database (and create a BCS external list to access the data).

– Are there existing apps using the current relational database? If yes, create a BCS external list to access the data.

– If no reasons prevent it, migrate the data into a custom list as this makes the solution less complex.

You need to make sure you play nicely and keep the data within the limits of capacity planning ( ). If there is absolutely no way that you can’t, keep the data where it is.