This article describes update KB3141459 for Microsoft Project 2016, which was released on January 3, 2017. This update has a prerequisite.
Be aware that the update on the Microsoft Download Center applies to the Microsoft Installer (.msi)-based edition of Office 2016. It doesn't apply to the Office 2016 Click-to-Run editions, such as Microsoft Office 365 Home. (How to determine?)
Be aware that the update on the Microsoft Download Center applies to the Microsoft Installer (.msi)-based edition of Office 2016. It doesn't apply to the Office 2016 Click-to-Run editions, such as Microsoft Office 365 Home. (How to determine?)
Improvements and fixes
Fixes the following issues:- Assume that you create and apply a grouping in a sheet type of view such as the Gantt Chart view in Project 2016. When you print the project, the horizontal bands appear. However, the vertical parts that tie together the top and bottom of the band don't appear.
- In Project Professional, you can now add the Locked field to a task view to facilitate closing tasks to update.
In Microsoft Project Server, team members have project tasks assigned to them and they report their status (the work that they have performed) on these tasks. In some cases, a project manager may want to close these tasks to update so that team members are prevented from submitting status but still have visibility to the tasks.
To achieve this, previously the project manager had to edit the project in Project Web App and set the Locked field on the given tasks in the project. Now, in order to lock or close tasks to update, the project manager can open their project in Project Professional and insert the Locked field into a task view where they can set the value to Yes or No as appropriate. - The Last Modified date in the Project Professional Open dialog box does not reflect the current time zone. For example, your time zone is Pacific Time (UTC-08:00) and the Last Modified date shows 09:15 instead of the expected 01:15.
- Assume that you save a project that has timephased baseline data to the XML format. When you open the XML file, the timephased baseline data is incorrect.
- When you save a baseline for a selected task, the task or assignment baseline values may be incorrectly rolled-up to and displayed on the related resources.
- When you apply status updates in PWA, actual work is added to some assignments unexpectedly. For example, suppose that you have an assignment that has 35 hours total work and the status update is to apply 9 hours. When you view the results in Project Professional, you find that the assignment is unexpectedly completed. Meanwhile, the total work and the actual work have increased to 400 hours.
- When you open a project from a SharePoint document library through a direct URL, the project is opened as checked-out even though the Require documents to be checked out before they can be edited? setting is enabled.
