Deprecated features in SharePoint 2013

Hi SharePoint friends,

I hope you all enjoyed my last post on “Authentication & Authorization”. In this post I will discuss about the features that have been removed in SharePoint 2013 which was available on SharePoint 2010.

  • Visual Upgrade: You could use this feature to upgrade from MOSS 2007 to SharePoint 2010 to give Site Collection Owner and Site Owner to preserve the existing user interface temporarily while still upgrading the infrastructure, content databases, site collections and features to the latest version. Now this feature is replaced with “Deferred Site Collection” upgrade which is considered as more comprehensive upgrade process than visual upgrade. Visual Upgrade preserved only the master pages, CSS files and the HTML files but the Deferred Site Collection upgrade with preserve much more including SPFeature functionality. With the deferred site collection upgrade you can use the UI feature from the previous version more seamlessly than with the visual upgrade. The key difference is that the granularity of upgrading the user interface is per site collection (SPSite) instead of site (SPWeb). Users can still view their site in SharePoint 2013 before committing. This is accomplished by creating and upgrading the temporary copy of the site collection. The reason for making the temp copy is once the site collection is upgraded, it cannot be rolled back.
    Note: Users who wants to upgrade from MOSS 2007 to SharePoint 2013 must upgrade first to SharePoint 2010 and then to upgrade to SharePoint 2013.
  • Document Workspace site Template: The scenario of collaborating on a document is provided by Team site in SharePoint 2013. This template will be removed in SharePoint 2013 and no longer supported in the next major release of SharePoint.
  • Personalization Site site template: This template was removed in SharePoint 2013 and no longer supported in the next major release of SharePoint.
  • Meeting Workspace site templates: This includes the Basic Meeting workspace, Blank meeting workspace, Decision meeting workspace, Social meeting workspace and Multipage meeting workspace.
  • Group work site template and Group Work solution: This template was removed in SharePoint 2013 and no longer supported.
  • Visio Process Repository site template
  • Imaging Web service: Since CSOM provides the client-side applications with access to the subset of SharePoint foundation server object model and Web Distributed Authoring and Versioning (WebDAV) provides the key functionality of the service, the Imaging web service was removed from SharePoint 2013.
  • Excel Services: This service was not completely removed instead the workbooks that have external connection can’t be edited in browser instead you are prompted to open the workbook in the client application
  • Web Analytics: This service was completely discontinued in SharePoint 2013 and are made as a part of search service. The Analytics processing component in SharePoint 2013 runs analytics jobs to analyze content in search index and user actions that are performed on SharePoint sites. When upgrading from SharePoint 2010 to SharePoint 2013 the web analytics service was not upgraded. The best practice is to turn off the web analytics service before upgrading to SharePoint 2013.
  • Organization Profiles

There are some other features that are deprecated in SharePoint 2013. Please go through the following URL to study the detailed description about the Search, FAST features that are deprecated in SharePoint 2013.

Deprecated features in SharePoint 2013 - Search, FAST

Still more to come…

Cheers…

Comments

  1. UnknownFriday, May 16, 2014 at 2:19:00 PM GMT+5:30

    Thanks for the information. I have just migrated from SharePoint 2010 to a free SharePoint 2013 site with http://www.cloudappsportal.com. Thanks.

    ReplyDelete

Post a Comment

Popular posts from this blog

PowerShell to update SharePoint Online User Profile property from Azure AD

Image
Hi Friends, in this post, I am gonna walk you through the steps to update the SharePoint Online User Profile property from Azure AD. You may think, why this is necessary since SharePoint online will sync automatically with Azure AD. The tricky part is the auto-sync may take up to 24 hrs to sync Azure AD to SharePoint UPS. The next tricky part is not all the AAD profile properties are synced to SharePoint UPS. Only a few of the properties are synced and below are the list of properties relevant to the profile that is synced to SharePoint UPS User Name First name Last name Name Office phone Department Job title Manager Office Office phone What about the other properties like 'Mobile Phone' that are relevant to the user??? What about if there is a drastic change in the Organization structure and you want the SharePoint UPS to reflect immediately??? To resolve all these obstacles and issues, we need to use PowerShell Now you understand why there i...
Read more

SPFx - Office UI Fabric react DetailsList & PropertyFieldCodeEditor to show the CSV data

Image
Hi Friends, this is a series of the post explains different capabilities of the web part using SPFx. Using DateTime control PropertyFieldCollectionData Property Pane Control Using FilePicker and FileTypeIcon control Office UI Fabric react DetailsList & PropertyFieldCodeEditor to show the JSON data Office UI Fabric react DetailsList & PropertyFieldCodeEditor to show the CSV data  --> You are here In this post, I am gonna show you how we can use  DetailsList   from  UI Fabric  and  PropertyFieldCodeEditor  property pane control from PnP on the SPFx web parts. The code walkthrough shown below will display the ' CSV ' data in the DetailsList. Regarding the creation of the basic project stuff, please refer to the  blog post . I hope those who are familiar with SPFx would know how to create the project and add the dependent npm packages. The following are some of the pre-requisites for the solution to work. Used  S...
Read more

Using React Context API in SPFx

Image
Introduction   Hi friends, this blog post will guide you through the usage of  Context API  which is one of the new features introduced in the latest version of React   in SPFx projects .  What is React Context and When to use it In a normal React application, the properties are passed top-down from parent to child and then to the grandchild via props. It works great in simple react applications, but this will be very tedious for complex applications.  Context  provides us an easy way to share the props without having them pass through all the intermediate components.  Context  should be primarily used when the properties must be accessible by many components at different nesting levels. We must apply it with cautious because sometimes it makes the reuse of the components more difficult. How can we use it in SPFx?   I hope many of you are aware of the SPFx development model, where we might need to pass the properties that are captured ...
Read more