I recently migrated my content database over to a new server and I have come across an odd problem.On one of my lists, there are two particular fields that I have set for mandatory. (They are not the only mandatory fields)When I fill out the form, and click save - it saves the list item as it is supposed to (as long as the mandatory fields are filled).I then go into the record again to add more information, the two fields in question are blank. I have to put the information back in so it saves.THIS TIME, if I go into the record AGAIN to add more information, the fields remain populated.Its a custom form, but its been working fine until the migration. I was thinking of tinkering with the form and trying to recreate those fields, but I figured I would ask first if anyone had any ideas?Thanks!

Update:I went in and basically wiped the customizations and kept the default form. I changed the order, and while the initial fields are fine now, one other field isnt holding its information on the first save, only after a second open/edit/save does it hold.

Hi,I cannot reproduce the issue, please go to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS to see if there has any log, and you can also find Event Log in Event Viewer. Let me know the result. Xue-Mei Chang

I apologize I never got back to this.The issue is still occuring - This is an abbreviated version of what happens.1. I have a list, the list has ~20 fields. 10 of which are mandatory to fill in2. I fill in the 10 mandatory fields. I save it, it DOES save3. I go to edit the list (its like a ticket request system) - 2 of the mandatory fields are blank.4. I then edit those fields again - save it - then edit it again.. The information in those fields sticks this time. It does not vanish.Its only happening to two fields that I know of. I have not tested EVERY field being filled in, but I will. I am mostly concerned with figuring out what is going on.I checked for the log file mentioned, I dont have one.I did not see anything out of the ordinary in the log file. Normally I think I would just nuke the list and start over, but there is now valuable data being stored in it, so that isnt really an option anymore.Help!

I did get this working, the customizations were minimal so I went in and deleted the custom list, and reenabled the default list. I tested it - it worked. So I tried creating the customizations again - it worked. Frustrating though. Any insight why this might be happening would be appreciated.

Hi BrianJSusol,I thoughtEvery custom list will be associated with a GUID, which will be stored in the Content DB.While migration the GUID in the Content DB and the Acutual Associated GUID for the custom list may not be matched.That's why when you remove the customization, it worked fine (Hope so).As per my understanding Migration involves lots and lots of discoverable things.Regards,-USK.