SP 2013: Duplicate field name was found after upgrading your SharePoint 2010 solutions to SharePoint 2013
Read OriginalThis article provides a solution for the 'Duplicate field name was found' error encountered when upgrading SharePoint 2010 solutions to SharePoint 2013. It explains that using reserved or system field names like 'Name' causes deployment failures after upgrade. The author shares a real project experience, showing how modifying the 'Name' property in field XML to a unique value resolves the issue. It also advises checking for code dependencies, data migration impacts, and list/view functionality. A practical troubleshooting guide for SharePoint developers handling solution upgrades.
Comments
No comments yet
Be the first to share your thoughts!
Browser Extension
Get instant access to AllDevBlogs from your browser
Top of the Week
No top articles yet