Its hard to keep track of what bugs were fixed a cumulative update. I intend to share my reading and document the fixes that come out every month across SharePoint products. Some call it regurgitating what’s already out there… but good luck finding it in Google search! Some updates aren’t cumulative – like Project Server 2013 June 2013 for one issue (see below). Hope this blog posts help someone some day!
Disclaimer: Cumulative Updates are to be applied specifically when you have an issue fixed by it, I recommend you keep a close eye on the security fixes that come with Cumulative Updates and then decide accordingly. Don’t rush to apply a Cumulative Update just for the sake of it. Many Cumulative Updates have had serious issues in the past and there’s no easy rollback! http://www.jeremytaylor.net/2014/04/12/latest-cumulative-updates-service-packs-hotfixes-sharepoint-sql/
Name: June 2015 Cumulative Update for SharePoint 2013
For previous build numbers: http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=346
SharePoint Foundation 2013 fixes
When you switch views by using the view selector for a document library that has the metadata navigation settings and the per-location view settings enabled, you are directed back to the root of the document library.
- When you use a REST call to fetch items with an expanded lookup field on a list that has many items with uniquely-defined permissions, you receive the following error message:
System.ArgumentException: Value does not fall within the expected range.
- If hundreds of resources are added to the project team, you cannot scroll to see the all the resources in the right-side grid of the build team page.
- This update translates some terms in multiple languages to make sure that the meaning of time zone settings is accurate in SharePoint Server 2013.
SharePoint Server 2013 fixes (includes the above fixes)
- Fixes the translation of the “Feel free to mention me in a post” link on My Site in a SharePoint Server 2013 installation that has the Polish language pack installed.
- Translates some terms on SharePoint Server 2013 sites in multiple languages to make sure that the meaning is accurate.
- Updates the English proofing tools.
- Fixes the following issues:
- Assume that you have a SharePoint search service application (SSA) that consumes a managed metadata service (MMS) from a remote farm through an MMS proxy. If you set this as the default MMS proxy and create a query rule that uses terms from the remote MMS, the query rule is not triggered because of a failure of the Query Classification Dictionary Update timer job when those terms are imported.
- When you update one of the metadata columns of a document set by using a client-side object model (CSOM), default values for the taxonomy fields are lost.
- The date and time on the Welcome page of a document set differ from the date and time in the View Properties dialog box of a document set when region settings on the site differ from those in the user profile.
- Assume that you have SharePoint search configured to crawl both internal and external sites. When you configure the proxy settings on the Search Administration page, pages that have friendly URLs do not appear in search results after a full or incremental crawl is completed.
- When you configure the query text in the query builder to contain a query string parameter, the results appear only for the first few pages on the Search Results Web Part.
- When you upload certain PFD files to a SharePoint Server 2013 document library, CPU usage spikes to 100%.
This update improves the performance of InfoPath forms solutions in certain cases for SharePoint Server 2013.
- When you apply a filter that contains many parameters to a SQL Server Reporting Services 2008 (SSRS) report, the report is displayed much smaller than expected.
- When you create a dashboard to hold a scorecard that has custom formatting in SharePoint Server 2013, the custom formatting is not applied to the scorecard. The scorecard uses the default formatting.
- When you use the Export to Excel function for an analytical grid on a business intelligence center site, you receive an “Access Denied” error message.
- This update improves the English proofing tools.
Security Updates in June 2015 for SharePoint Server 2013:
Project Server 2013 fixes (does NOT includes all the above fixes – see last point)
- You add a nonstandard line for a task in your timesheet, add actual work to it, and then save the timesheet. In this situation, the actual work for the same day is replicated onto the standard line. Therefore, the total actual work is doubled.
- In Project Web App, when you create a project from a template in which a budget resource is assigned to the project summary task, the project cannot be published. Additionally, you receive an error message that resembles the following:
Your new <project_name> has been created successfully, but failed to publish and will not be listed in the Project Center.
- Tasks and approvals are not displayed on the home page in Project Web App when the Polish language pack is applied.
- After you use the Turn in Final Timesheet function to send a timesheet in Project Web App, the timesheet can still be edited and saved.
- From a project detail page in Project Web App, you save a project that contains cost resource assignments. In this situation, the costs on the assignments may change unexpectedly. For example, a cost of $1.16 changes to $1.00.
- In Project Professional, assume that a summary task is edited in such a way that its subtasks are hidden, and the plan is later published to Project Server. However, when you edit the project in the Schedule Web Part in Project Web App, the previously hidden subtasks cannot be displayed and edited.
- When you import external data from an OData data feed to a workbook in Microsoft Excel 2013, you receive the following error message:
The content of the data fee is not valid for an Atom feed.
This issue occurs if the data feed has a custom field that has a lookup table and a graphical indicator.
- When you apply a grouping to a view, and the view contains an enterprise custom field that has a formula, the values from the custom field do not roll up into the grouping row.
- When you create a project that’s based on a template in Project Web App, you do not become the owner of the project. This means that you cannot see it in the project center. Additionally, the user who created the template is set as the owner of the project.
- After you rename a custom field that’s used in a timesheet, the changed field name is not displayed correctly in the dbo.MSP_TimesheetLine_UserViewCF table, and it may be associated with another field.
- When you set a SharePoint list indicator on a timeline Web Part on a SharePoint Server 2013 site, a duplicate timeline Web Part is displayed when you refresh.
- In single entry mode, after you submit a timesheet, the timesheet manager can adjust the time that you submitted. However, these changes are not reflected in the tasks in the project. This means that the work that was recognized in the timesheet in out of sync with the project.
- When you save a project in Project Professional or Project Web App, custom field values are lost.Note This issue occurs after you apply March 10, 2015 update for Project Server 2013 (KB2956178)
- In Project Web App, when you create a project that’s based on a template, the tasks do not have the TaskOutlineNumber field value that’s set in the template. This is reflected when you view the data in locations such as the dbo.MSP_EpmTask database table.
- When you update a plan by submitting updates through a timesheet or tasks in Project Web App, auto approval rules may not apply the update. Instead, the approval appears on the status manager’s approvals page.
- The Configure Columns settings (for example, column width, or order) on a timesheet are reset unexpectedly to the default every time that the timesheet is refreshed.
- When you publish a project that has a task marked as a milestone in Project 2013 to a Project server, the task is not displayed as a milestone in the timeline view in Project Web App.
- To fix the following issue for Project Server 2013, install June 9, 2015, update for SharePoint Foundation 2013 (KB3054867):
You cannot scroll to see all the resources on the right-side grid of the build team page if hundreds of resources are added to the project team.
Office Web Apps Server 2013 (excludes the above fixes)
The Decrease List Level and Increase List Level functions are unavailable in PowerPoint Web App in the Chrome web browser.
Security Updates in June 2015 for SharePoint Server 2013: