Custom displayform and editform migration

Question

Hello:

I recently came across an issue while doing a testing a migration of wss3.0 to Foundation 2010.  The issue revolves around a list that the customer created some custom display, edit, and new form using SPD2007.  The migration is overall successfull with the exception of the editform having issues.  When we try to edit an item within the list in the 2010 farm, it displays the form but it looks all skewed and the rich text box areas appear corrupted with wingding characters.  What I don't understand is how these forms are carried over to Foundation.  I see the display, edit and new forms when I open the list in SPD2010 and when I try to edit the "editform", it doesn't appear to be the one associated with the list.  It is very confusing to look at the list in SPD2007 and then looking at it in SPD2010.  Not sure how I would get this fixed so any assistance would be appreciated!!

AT

Answer 1

Hi,

Thank you for your question .I am trying to involve someone familiar with this topic to further look at this issue.

Thanks

---

Entan Ming

TechNet Community Support

Answer 2

Thank you, Entan!  What I have further discovered and can not figure out is this:

I see the DispForm.aspx, EditForm.aspx, and NewForm.aspx are default dispay, edit and new forms for the list.  However, the list doesn't appear to be using these forms for displaying, editing or creating new forms.  They seem to be pointing to another set of display, edit and new forms which have different names.  It almost seems as though the list has something hardcoded to look only for those specific form names.  I tested this by renaming the default display, edit and new forms to the name of what it actually is using and it now seems to be using those forms.  I'd like to know how this list is only looking for specific form names??

Answer 3

Hi - any update on this yet?  Thank you.

Answer 4

Hu Rumi,

The custom forms most likely will come over in the migration from 2007 to 2010, but if there are any forms that don’t work as expected, they will need to rebuilt in 2010 and then set as the default.

Gregg

---

MSFT

Answer 5

Gregg,

Ok - thank you.  But can you answer this for me please as I had posted before:

 see the DispForm.aspx, EditForm.aspx, and NewForm.aspx are default dispay, edit and new forms for the list.  However, the list doesn't appear to be using these forms for displaying, editing or creating new forms.  They seem to be pointing to another set of display, edit and new forms which have different names.  It almost seems as though the list has something hardcoded to look only for those specific form names.  I tested this by renaming the default display, edit and new forms to the name of what it actually is using and it now seems to be using those forms.  I'd like to know how this list is only looking for specific form names??

Thanks,

Answer 6

Hey Rumi,

I haven't seen that specific issue before where you can't set a specific form to be the default or create a new form and then set that as the default.  I understand you can rename the default forms to the actual form name the list is using, but I haven't seen an issue where a migrated list uses hard coded forms.  You may need to open a support case to work on this further if you can't re-create or set existing forms to be the default. 

Gregg

---

MSFT