• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 556
  • Last Modified:

Using Sharepoint Designer 2010 on a list migrated from SP2007

I have customised the New, Edit and Display forms for a list in Sharepoint and Sharepoint designer 2007. Following that, a database attach migration was completed. I am now having issues opeing the forms. e.g. This happens when I attempt to create a new item in the list.
(I have several fields using the Sharepointboost Cascaded lookup)

System.NullReferenceException: Object reference not set to an instance of an object.
   at Brandysoft.SharePoint.LookupPro.CrossSiteLookupField.HandleTextBoxChoices(TextBox textBox, Func`2 predicate)
   at Brandysoft.SharePoint.LookupPro.CrossSiteLookupField.Internal_CreateChildControls()
   at SharePointBoost.Util.TryCatch.Run(CodeToRun codeToRun, CatchCode catchCode)

I don't believe that it is not the cascaded dropdown itself, because another application using it and migrated in the same way works well. (same farm, same app pool)

The first thing I want to do is set one of the uncustomised forms back as being the default, without destroying what I have (ie setting the current one back to the site definition is not an option)- I have saved EditForm1.aspx, Editform2.aspx etc as well as the original. Being able to do this will help me step through my customisations and locate the source of the error.
How do I do that in Sharepoint Designer 2010?.
What is displayed in the list settings - forms area.As the attached image shows, Sharepoint Designer only displays that  the original forms are default? - which is not correct, because when I try to create a new item in SP2010, it uses my correct default form (NewForm2.aspx as specified back in SP2007)

Thanks in advance.
MKA
0
M_K_A
Asked:
M_K_A
  • 4
1 Solution
 
KoenVostersCommented:
It is a crossitelookup field. Can it be that the cross site has moved to another url? And that the other one is working because the url's stayed the same?
0
 
M_K_AAuthor Commented:
KoenVosters,
Thankyou for your comment. Unfortunately, it is not a cross site lookup. The cascaded lists are all in the same site. There is no access to the URL information for the lists used in the cascaded lookup, and considering that it does work on another site, I would expect that there is not an issue based on hard wired URLs. Good  line of thought though - thankyou. I have raised the points from 50 to 250 as it is obviously not a simple solution.
Regards, M_K_A
0
 
M_K_AAuthor Commented:
Further information:

The issue is resolved if I am local administrator on the SP2010 server. It fails for all users who are not local admin with the above error message. Obviously I don't want to make everyone a local administrator!
M_K_A
0
 
M_K_AAuthor Commented:
Solved the reason for the error message. It was because the cascaded dropdown was referring to a list with about 13000 items in it, and the default list throttling setting for SP2010 was set to the default 5000.

This still doesn't answer why a migrated application from SP2007 to SP2010 doesn't display which are the default forms for a list correctly.

Closing this call.
0
 
M_K_AAuthor Commented:
I accepted my own comment as a solution because it resolved the problem.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now