List Properties Supporting Files Display item form won't stay set

ME TOO!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Any help would be appreciated.

So far I haven't found a work-around. Renaming DispForm.aspx doesn't work. Deleting it won't work either.

Here's something. I tried to edit the default DispForm. I unattached it from the page master, deleted everything in the file and then added my own contents.

Now the supporting file field is blank - just the same as if I deleted DispForm.aspx.

So, either there needs to be something special in the file, or it needs to be attached to a page master.

hank

Hank--I think you're onto something, something special does need to be in the file.

In my readings / findings I have been able to work around it (so far maybe kinda sorta). The trick is to use the aspx's that are provided: dispform.aspx, editform.aspx, etc and hide the existing web part zone. It seems that the original web part needs to exist (but can be hidden) for custom forms to work and thus the supporting files need never be changed.

Note: Make sure you save the page after each step or the menu items will be disabled.

1. In Sharepoint Designer goto the existing web part zone and turn it's visiblity off (Visibility="false"). It seems to work best if you hide the web part zone and not just the web part. Play around with this if you like. I've had inconsistent results hiding the zone vs. the web part. Sometimes the original likes to show itself again even though it's turned off. Weird.

2. Next and with the cursor inside the "PlaceHolderMain" area click Insert -> Sharepoint Controls -> Web Part Zone.

3. Next and inside the new web part zone click Insert -> Sharepoint Controls -> Custom List Form. In the list / document library drop down box select your collection name. In the content type drop down select the type that suits your needs. Select the type of form to create: New / Edit / Display.

4. In your new form navigate to the <Xsl> tag and have at it. If there is not an <Xsl> tag, right click on the new form in "design view" and click on "Convert to XSL View" (or something like that).

So, this is what I've been able to determine and it is definitely NOT a full proof work around. Sharepoint Designer is quirky at best and I've still have had to "tread lightly" (thanks to the person who suggested that). I'm quite concerned about this bug as it impacts future maintenace. What if a year from now updates are made and the links to the dispform stop working Ahhhhh, I think I'd sell everything and move to Redmond. Please, Microsoft, Help.

~Jibran

P.S. It's been added to the KB, by David: http://support.microsoft.com/Default.aspx id=935504

I've had a result from my Microsoft product support case that works:

Hi Leroy,

I¡¯ve had a response back to my query regarding content types.

The problem we were experiencing was that we were not setting the correct content type. If you look at your list settings it will show the content types available. By default you only have Item.

When you are modifying the supporting files tab you need to specify the content type that will be used for these supporting files.

Please change the dropdown from Folder to Item and see if that works in your environment.

Regards,

Andrew Purdon

Yes, but that solution only works when you have one content type.

In my list I have two content types, and it is only possible to set the forms for one of them. If you try to set values for both types Sharepoint Designer responds that there is a "save conflict with another user".

If you first set the values for one of the content types, closes the properties window, and then set values for the second type, nothing happends.

/paanvst

I am having a similar problem. I am able to update the List Property setting (Display) Item Form value to point to my custom page, if I change the Content type selection to Item first... BUT the links that should take the user to the custom form now are http://[myWSS_Server]/ ID=1 instead of http://[myWSS_Server]/Lists/ListName/CustomPage.aspx ID=1

I have seen a few other posts with this exact issue, but no solution listed. Does anyone have one, other than creating a new list