Overview of the issues that are fixed in SharePoint 2013 SP1

This information is a crosspost from:


SharePoint 2817429​ Metadata is lost when documents   that use a custom content type with a “Description” field are   opened for editing.
SharePoint 2817429​ When an item is deleted,   restored from recycle bin, and then deleted again, there is a primary key   constraint error.
SharePoint 2817429​ An error occurs when files are   moved between document libraries and the web time zone is behind that of the   server.
SharePoint 2817429​ Metadata filtering at list level   always lists all metadata terms.
SharePoint 2817429​ The hyperlink popup window drops   the selected word to be linked when there is a delay of more than one second   in opening the window.
SharePoint 2817429​ Multiple-column,   SummaryLinkWebParts with a group heading style of “Separator” are   rendered incorrectly.
SharePoint 2817429​ A hash tag that contains a full   width space does not get created successfully.
SharePoint 2817429​ Search schema compression is now   enabled by default to allow larger search schemas.
SharePoint 2817429​ Highlighting for FQL queries is   now enabled for FQL as well as KQL.
SharePoint 2817429​ Opening a custom SharePoint list   in datasheet view and applying multiple custom filters, where each filter has   more than one condition, can result in an incomplete set of list items.
SharePoint 2817429​ When the “Export to   Excel” button is clicked in a SharePoint document library that has the   Content Type field displayed, the Content Type field does not appear in the   Excel workbook.
SharePoint 2817429​ An error occurs after changing   the “Manager” property in EditProfile.aspx page when the My Sites   WebApp is not in the same farm as the UPA.
SharePoint 2817429​ SharePoint REST API does not   return a well-defined error response for a duplicate key exception.
SharePoint 2817429​ Developers are unable to specify   a Content Type ID when creating Content Types in the client object model.
SharePoint 2817429​ On list views in SharePoint   sites, the Connect to Outlook button in the ribbon may be erroneously   disabled.
SharePoint 2817429​ In some non-English languages of   SharePoint, the text displayed in the callout UI for a document or list item,   describing who last edited the item, may not be grammatically correct.
SharePoint 2817429​ Copy and Paste in a datasheet   does not work correctly with Internet Explorer 11.
SharePoint 2817429​ Pages do not render in Safari   for iPad when private browsing mode is used.
SharePoint 2817429​ When editing rich text fields in   SharePoint, if the editing session exceeds 30 minutes, the edits may not be   saved.
SharePoint 2817429​ An error that says   “SCRIPT12004: An internal error occurred in the Microsoft Internet   extensions” may occur intermittently when users visit their SkyDrive Pro   or other pages on their personal site.
SharePoint 2817429​ InfoPath may crash when a form   that points to a SharePoint list, with a lookup to another SharePoint list,   is opened.
SharePoint 2817429​ An InfoPath form with extended   characters in its name fails to open.
SharePoint 2817429​ An error that says   “Security Validation for the form has timed out” may occur when an   InfoPath form is digitally signed and hosted in a SharePoint site collection   that uses the SharePoint version 2010 user experience.
SharePoint 2817429​  “Show document icon” remains   unchecked and the document icon does not show in Edit Properties for a list   item.
SharePoint 2817429​ A “Failed tagging this   page” error occurs when the “I like it” button is clicked.
SharePoint 2817429​ The wrong term is removed when   manually editing a multi-valued taxonomy field.
SharePoint 2817429​ When tagging list items using a   language that is different from the term store default language, suggestions   for labels are offered in multiple languages. The suggestions appear   confusing because both language suggestions are listed without any identification   of the language.
SharePoint 2817429​ An error that says “There   was an error processing this request” may appear when editing the user   profile.
SharePoint 2817429​ Times are missing from Date/Time   results in certain filtered list web service calls.
SharePoint 2817429​ Minimal and no metadata are now   enabled as supported JSON formats.
SharePoint 2817429​ Actions4 schema workflow actions   can’t be deployed to SharePoint.
SharePoint 2817429​ Using Client Object Model,   Stream.Seek() to seek to a particular position doesn’t seek at the proper   offset.
SharePoint 2817429​ Refreshing a workflow status   page generates the following error:   “System.Collections.Generic.KeyNotFoundException: The given key was not   present in the dictionary.”
SharePoint 2817429​ Setting custom, non-English   outcomes in web pages on tasks in a workflow fails to set the value.
SharePoint 2817429​ Configurations of SharePoint   using Azure Hybrid mode and Workflow Manager together can cause workflow   callbacks to fail.
SharePoint 2817429​ Workflow task processes on wiki   pages won’t start.
SharePoint 2817429​ Workflows won’t wait for changes   to content approval status fields.
SharePoint 2817429​ E-mails generated by workflow   cannot be disabled for approvals in SharePoint workflows.
SharePoint 2817429​ Workflows may fail to send an   e-mail or send too many e-mails.
SharePoint 2817429​ Association variables do not   update correctly for auto-start workflows.
SharePoint 2817429​ A KeyNotFoundException error may   occur in a workflow when the associated task list uses unique permissions.
SharePoint 2817429​ Incomplete tasks are deleted   when workflow task activities complete.
SharePoint 2817429​ Task activity is suspended when   the task is completed using app-only credentials.
SharePoint 2817429​ An error that says “This   task could not be updated at this time” occurs when trying to complete a   workflow task using the “Open this task” button in Outlook.
SharePoint 2817429​ A workflow doesn’t respond   properly when waiting for changes in specific types of list columns, such as   Boolean, Date Time, and User.
VN:F [1.9.22_1171]
Rating: 9.5/10 (4 votes cast)
VN:F [1.9.22_1171]
Rating: +1 (from 1 vote)

SPUtility.GetGenericSetupPath is obsolete, long live SPUtility.GetCurrentGenericSetupPath & GetVersionedGenericSetupPath

Whenever you are in a scenario where you need the location to the SharePoint root directory on the server in the farm that is executing your code, do NOT hardcode the path like the example below:

Bad practice:

private const string rootfolder = "C:\\Program Files\\Common Files\\Microsoft Shared\\web server extensions\\14\\";

The location of the SharePoint root directory depends on the configuration during the installation of SharePoint, your code will break if this configuration is different.

As you probably already know, it is a recommended practice to use GetGenericSetupPath available in the static SPUtility class. Please be aware that this method is obsolete in SharePoint 2013 and we have 2 new methods:

This will help you to make sure that your code is generic enough to deal with all scenario’s. For example with site collection upgrade.

Hope it helps!

VN:F [1.9.22_1171]
Rating: 10.0/10 (2 votes cast)
VN:F [1.9.22_1171]
Rating: +1 (from 1 vote)