Pål Amundsens blog

How To Create A SPList Of An Existing Type

paalam — Mon, 17 Jul 2006 19:33:14 +0000

I’ve found that creating lists in site definitions using CAML is fearly well documented. However, when it comes to creating a list programmatically, I didn’t find what I was looking for –until this enum emerged on a russian site: SPListTemplateType. Of course, I’ve later found it in the SDK as well, but again – I didn’t find it where I’d expect it to be.

So here you go:

How To Sign Up For Events On A List Using Javascript

paalam — Mon, 17 Jul 2006 19:26:43 +0000

The object model actually only supports event handling on document libraries. However, you can easily hook up to events on other lists using javascript. Let’s say you want your own code to run whenever a listitem is deleted by a user, like in the picture below:

The easiest way to do this is to add a Content Editor Web Part and add the appropriate javascript code in the Source Editor:

You can now get the ID of the listitem that the user selected for deletion by referencing the object id : currentItemID.

Doing this will actually override the original deletion of the item that is done by ows.js. This means that you also have to write code in the DeleteAndDoSomethingElse-page to actually delete the item.

Sharepoint Profile Import With Trusted ADs? Specify The Wanted Domain Controller – Don’t Use Auto Discover

paalam — Fri, 14 Jul 2006 16:24:08 +0000

A company I work for recently added a trust between two domains. This gave me some challenges on how to import user profiles from both domains. I set up two different connections on the Manage Connections page (http://server/_layouts/1033/MgrDSServer.aspx), set the Search Base with no OUs (just DCs), but soon realized that the trusted domain had a different structure – giving me over 7000 new users in stead of 300! Stupid me. It turned out that the trusted domain had contact objects for people from all over the world – and these were of course imported into Sharepoint together with the rest.

The solution seemed easy enough – just add an OU to the Search Base. -Mistake no. 2. There were two top-level OUs – not one. So how could I combine the two sets of users in one connection? (You cannot add two connections to the same AD in Sharepoint) I found a great solution in this blog: http://mindsharpblogs.com/wayne/archive/2005/06/15/497.aspx and this page: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adsi/adsi/search_filter_syntax.asp

This lead me to changing the LDAP search filter (User Filter in Sharepoint) in stead of the Search Base, so that it combined users by getting them from two AD groups. Here is the search filter I ended up with:

(&(objectCategory=Person)(objectClass=User)(|(memberOf=CN=UserGroup1, OU=Groups, OU=Accounts, OU=OUGroup1, DC=local, DC=dk)(memberOf=CN=UserGroup2, OU=Groups, OU=Accounts, OU=OUGroup2, DC=local, DC=dk)))

Great! Except one thing – this syntax worked only when specifying a domain controller – not when letting Sharepoint auto discover it. Why beats me. I’m sure there’s some AD expert who could answer why, but I’m just glad I found out! By the way – the same thing happened when using LDIFDE – also there I had to specify the domain controller (with the -s operator).