ReadOnly change creating very unexpected behavior
So an interesting little work around I have been using to export/import web parts from one web site to another is to save the list as a template while including the content, then import that template on the new site, and create that web part from the template with my data. This worked fine for most cases, but the created by and modified fields were based off when I created the web part, so they were all the same time and created by me. A work around to that I used was to go into the ONET.XML file on the server and change the ReadOnly property on the list to FALSE, restart the IIS and edit the column. Unfortunatly this only works for lists made from that site, not imported templates. To get around that I changed the .stp template file to a .cab, extracted the files, changed the ReadOnly property in the manifest.xml to FALSE. Then I archived the files back into a .cab, and changed the extension to .stp. I imported the template on the new site and created the list from the template. Now here is where my problem began. While the solution allowed me to change the created by field, when I imported the data the created by field was no longer filled by me. Instead there appeared to be a random selection from AD of people for the created by field (out of over 100 items on 1 was correct, and many were blank). I changed all the created by to the correct person. My problem occurred when I tried to do this for a discussion. While I could change the created by field for most of the discussion items, some gave errors. I was changing the column in a datasheet view for both discussion and the previous list. Off the top of my head I cannot remember the specific error (I will edit it in here), but it was a failure to update error and gave me the option to try again or discard changes. To summarize my problem: List: No problem changing created by for all the items. Discussion: Could change created by for most of the data but not all. This was done in a datasheet view. Any tips on what could be causing this error or a way to work around it?
July 28th, 2010 5:20am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics