Edit/Display form does not show site columns after upgrade


Hi all,

I don't think this is related to the above question, but the linked "solution" is as good as I can come up with, however it looks like its possible that ALL the libraries in the collection are suffering the same situation...


our site was migrated to 2013 from 2010 from 2007 and is running in compatability mode around 6-18 months ago. I'm pretty sure the old system is gone too - database backups might be obtainable... not sure.

There are a bunch of "site columns" that are used consistently across the collections libraries (there seems to be a general avoidance of "content types", don't ask me why, I don't know, I also don't know what would be involved in moving them all to content types as many of the sites "views and webparts" use the content type columns to surface things all over the place, so I suspect it would be a big job), but folks have recently noticed that some documents are missing from various pages (webparts that are gathering documents from these columns values).

But the problem is that it seems that since the update most (all?) of the document libraries NO LONGER enforce the requirement and litterally only show "name*", and "title" in display and edit properties...

Any ideas on how to get things back to showing the "proper" forms (I can only guess what this was from documentation and screenshots and general guessing based on the "commonness" of the columns in question)? Or is there a way to merge or migrate "columns" to content types in some way that is either "collection wide" or non-breaking?

ANY assistance would be greatly appreciated!

November 20th, 2014 12:48am

Hi noJedi,

We are currently looking into this issue and will give you an update as soon as possible.
Thank you for your understanding and support.

Daniel Yang
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com. 
Free Windows Admin Tool Kit Click here and download it now
November 21st, 2014 9:43am


Thank you for your patience.

I understand some documents are missing after we migrated to SP 2013. Based on my experience, if we are using attach database method to migrate from previous SharePoint to SharePoint 2013, some site may have issues. This is because the framework have some difference beteen SharePoint 2013 and SP2007/2010. In addition, if the site have customized page, these site will also have some issue. So we recommend that we need to re-create the site in our new SharePoint 2013 environment.

If you have any questions, please feel free to let me know.

Best Regards,

Dats Luo

December 4th, 2014 6:06am

So just to be sure are you saying that '2010 compatabilty mode' is causing these issues?

Just to be SUPER clear from my end this is what I'm seeing as an example;

  • For a collection
  • with site columns
  • many but not all lists
  • many but not all list items

--> are missing valid data in the site columns that have been registered for that list.


name          modified by    doctype     department

item1.docx   username   <blank>  <blank>

item2.docx   username    WorkInstruction    Planning

if you click "edit properties" you are presented with ONLY the (I'm guessing) content types fields (eg: for Document you get Name and Title) and NONE of the other fields that should be specified.

However if you hit "save" you can see that the data in these fields returns to the "list view" (however it does not re-enable these fields from being active in the View/Edit properties pages).

Is this something that can be fixed? Or are you saying that we need to backup the DB and restore to a FULL version (not in compatability mode) of SharePoint2013? Or are you saying we need to revert to our PRE update backup and do something?

Its been many months since thsi upgrade was done and the system has changed a lot, so you can imagine we are reluctant to loose much of these changes...

Free Windows Admin Tool Kit Click here and download it now
December 9th, 2014 12:42pm


Sorry for the long time to research.

We can't restore SharePoint 2013 farm from SharePoint 2010 backup directly. We need to use database atach method to migrate from SharePoint 2010 to SharePoint 2013.

And i would like to know if there is any questions about the the upgrade progrss?

Best Regards,

Dats Luo 

December 24th, 2014 10:02am

Hi Dats,

We have already "attached" as our migration method.

This strange behaviour is occurring over the 4-6 months since the migration and is only recently being reported by users and fault found down to the information I've presented above.

As far as I know we did not experience any errors or warnings in teh upgrade process.

However I note that search results are questionable at times.
User profile/AD integration appears to be either very slow to update or there are some things that simply aren't updating - I can't see any errors in the logs regarding this, but its very hard to see given the volume of data in the logs.
I've also posted another query about files (usually infopath .XML, but occasaionally others) being "unable to save as its lock by another user" (only to find in the logs that its locked by the same user that is using... eg: dmn\myuser is the user and the log reports something like - "unable to save file is locked by dmn\myuser"

If you have any information on this/these problems I'd be greatful, but as it is I'm thinking this is beyond me because of time and knowledge constr

Free Windows Admin Tool Kit Click here and download it now
January 30th, 2015 8:49am

Hi this is still an issue, however while I don't really undertstand what this does at a fundamental level, the "Relink documents" description SOUNDS like it might be able to do correct the issue I'm facing.

Can anyone clarify what this option/function does and let me know if this is something worth investigating?

August 12th, 2015 3:32am

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

Other recent topics Other recent topics