Thursday, March 19, 2009

Challenges and limitation while saving list as template from SharePoint GUI

I have found some limitation when I was tried to create new list from existing list template from SharePoint GUI, suppose we have 2 list and one list has lookup column associated with second list column, now we are saving or exporting both list as template and including content to migrate both list from one server to another server, when we are creating new list from saved template, at that time, we are not able to see lookup column values into first list and we are getting error “One or more field types are not installed properly. Go to the list settings page to delete these fields



I need to go into first list and again map lookup column from second list column, because while migrating list from SharePoint GUI, it didn’t keep column relationship mapping. By using 3rd party tool like AvePoint for list migration, we won’t face such type of error. We can also write custom code to migrate list from one server to another server.

Friday, March 13, 2009

Data view web part – rich HTML text problems/output caching

While working in Data View web part, I have placed user name column into my data view web part, but by default, it displayed some rich text HTML into page, in this case, we need to disable output caching for web part, so for this, we need to put disable-output-escaping="yes" tag into XSL.


e.g. <xsl:value-of select="@fieldname" “disable-output-escaping="yes">


Problem with "doctype" column name into SharePoint List

I was faced problem with column name “doctype”, I was not able to create “doctype” column with any of the data type into SharePoint List, and I was getting “Unknown error” into my page when I tried to create column. I tried to find the solution on the internet for some time, but I didn’t get good information, I believe that “doctype” column name is reserved for internal purpose, so we can’t use same name like ID, title column name.


Luckily I was able to create “doctype” as single line of text data type, now the actual problem started, I was not able to delete “doctype” column from SharePoint list, definitely we can write custom code and delete same column from code. But I have found easy way to delete “doctype” column from going to tool called “SharePoint Manager 2007” and I have selected my site-> list -> “doctype” column and delete from that tool. You can find more information regarding SharePoint manager 2007 from my blog, here is link


Now if we have requirements to create “doctype” into list, then we can create same column name by changing character case. “doctype” column name is case-sensitive, like we can create column with named “DocType”

Tuesday, March 10, 2009

Locking down SharePoint Designer (SPD)

One day, I was getting “This web site has been configured to disallow editing with SharePoint Designer. Contact your web site administrator for more information” error while opening my SharePoint site from SharePoint Designer (SPD), after that I have found that one of my admin people change into site definition file onet.xml to restrict us from opening SharePoint designer.


Actually we have faced lots of problem while considering SharePoint site access, because when we were giving designer or full control rights to any users for SharePoint site, they can do customization from SharePoint Designer (SPD) tool also, but as per our requirements, only admin people can do customization from SPD, user who has designer or full control rights into SharePoint site, we would like to control them from using SPD tool.


I spend good amount of time for finding out the solution, but till now I didn’t find any exact and perfect solution which will best suites and fits for my requirements, because in SharePoint site, all permission are dependent on each other, so if I remove access for ‘Add and Customize Pages permission” level then “Manage Web Site” permission will be also remove from Site Permission section.


We can control and lock down SPD In below level.


  1. Site level, it’s prevent user from opening all site created from specific site definition

  2. Web Application level for all users

  3. Web Application level per users or groups

  4. Site collection level

  5. Site collection level from SPD(Contributor settings)


We can find many good information regarding how to lock down SPD, but guys believe me that below link giving me very good useful information and main thing, it combine and describes all possible way into one article only.


I’ll update my post; if I find any proper solution to locking down SPD for particular set of users with full permission access into SharePoint site from GUI.


Reference Link: Link contains very useful information describing user security for locking down SharePoint Designer. : how to change onet.xml file for disallowing users from opening SharePoint Designer