This security update contains the following nonsecurity improvements and fixes for SharePoint Server 2016:
- Enables Access 2016 application packages to be installed in SharePoint Server 2016 on-premises version together with SQL Server 2017.
- Fixes the following issues:
- When you search by using path search and the file name is longer than 961 characters, the search doesn’t return any results, or the results aren't as expected.
-
When a SharePoint site contains a document set that's stored in new site collection, another web application, or another content database, you can't add a new document by using the “Document Set” content type. In addition, when you try to access an existing document in a set, you receive an error message resembles the following:
Sorry, something went wrong "File Not Found.''
- Some ribbon buttons incorrectly appear grayed out when you select documents.
- When you have a User Profile service application configured but don’t have My Site configured, the SharePoint users can't access the My Language And Region setting.
- You can't filter items on Content Type by using representational state transfer (REST) application programming interfaces (APIs).
This security update contains the following nonsecurity improvements and fixes for Project Server 2016:
- Assume that a Project Web App site is configured to use Host Headers for the site collection. In this case, the drop-down menus on the Force in/out field for the project selection in portfolio analyzer views don't work correctly.
- In some cases, the timesheet status is displayed as "Not Approved" even though the timesheet has been approved.
- Consider the following scenario:
- You have a Project Server 2016 and a Project Web App instance provisioned.
- You have at least one resource defined.
- You log on the Project Web App site instance, locate the Resource Center view, select a resource, open the Resource tab in the ribbon, and then select the Capacity Planning button.
- In Capacity Planning views, you look for the Export to Excel button to export the details table.
In this situation, the Export to Excel functionality is missing because the button does not exist.
- Consider the following scenario:
- You have a task that has a resource assigned.
- The task has a split in it. For example, there's a week of work, a week with no work, and then a final week that has work.
- In the timesheet for this task, you enter hours on the task so that the work is completed up to the date where the split begins.
- The timesheet is submitted and then the status update is approved.
- After that, the project is opened in Project Web App, and the task finish date is adjusted to a date that’s after the actual work is completed. For example, the actual finish date is set to the middle of the week where there is no work.
In this situation, the actual work is spread over the whole duration.