Monday, May 15, 2017

Components that could break after SharePoint upgrade

Although you can predict most of the stuff that could go wrong after a SharePoint upgrade or migration but still there are chances that you miss something. I have compiled a list of components that could break or stop working after you move to new SharePoint environment. I'll be updating this post whenever i found anything else breaking after SharePoint upgrade. I apologize for my rough formatting. :)

Connections with external services and libraries.
Connection with User Profile Service Application.
When upgrading to 2013 from 2010, you need to update where fetching User Information like User Name User Friendly Name. SharePoint 2013 works on Claims Based Authentication so InfoPath 2010 Form Views may crash if you are showing view on user based.

OneNote Sync URL change
OneNote not syncing

Static URLs:
Static URL's used in Web Pages, Always use relative URLS

Connected Excel Files:
Data exported in Excel files could break if URL change after migration

SharePoint URLs in Workflow emails
Bindings of Users like Created By, Modified By could break with blank or a GUID showing in text box

Shared Calendars:
Shared Calendars are bind with a URL, If the URL changes after migration or upgradation, that might break the Calendars.

Custom JS/CSS:
If you have some custom pages which contains some custom JS or CSS and has to deal with something on the page, there is a strong possibility that it might break after the migration. As the master pages and layouts are different in MOSS 2007, SharePoint 2010 and SharePoint 2013, there could be a chance that your JS or CSS dealing with SharePoint's tags no longer work after upgrade.

No comments:

Post a Comment