SharePoint – Autocomplete followup, New view and Edit view

I wrote this post about autocomplete in the advanced search box.

There’s another place where this would come in handy, the “Create new view” page and “Edit view” page.

Now, if you use the JavaScript from the previous post you can simply just add this JavaScript to your document ready and get suggested results in you create and edit view pages as well.

This will help the user to create more efficient views because they don’t have to check which metadata is available.

As you can see, this will work where ever you want as long as you set the currentTextBox and get the propertyValue.


SharePoint – The column name that you entered is already in use or reserved.

I encountered this problem in a WSS 3.0 environment. Hopefully this can help newer versions of SharePoint as well.

The scenario

My customer has a old WSS 3.0 environment with a huge site collection. It’s a root-site with 200 sub sites with sub sites. This is a free for all SharePoint with no boundaries. Which makes the maintenance a pain in the ass.

The problem

Someone (with to high permissions) renamed the built in field “Title” to “DayReportDate” on the root-site and published it over all sites changing all content types that inherit from Object.. which is well, all. And users on sub sites discovered this pretty quickly and changed their child content types title field back to “Title”. This caused a huge problem since when trying to rename the root-site title field back to “Title”, SharePoint would say “The column name that you entered is already in use or reserved.” even if it’s just reserved on one of the sub sites.

Everyone panicked because their title field was changed to “DayReportDate” and more than 200 sites where affected by this mistake. Having this problem for 6 months they decided that someone with SharePoint experience should take a look at the problem so the case landed on my desk. Yippie!

A problem for me was that I had no server access, so I could not create a console application (or likewise) using the SharePoint server API to correct it. And since it was WSS 3.0 there would be no PowerShell either. So I simply had to fix it on the client side.

I found two solutions.