October 11, 2016, update for Project 2016 (KB3118342)

This article describes update KB3118342 for Microsoft Project 2016, which was released on October 11, 2016. 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?)

Improvements and fixes

Fixes the following issues:

• When you open projects from an XML file and some tasks in the file are defined as manually scheduled, the duration of these tasks may change to the default of 1d instead of the value that's defined in the file.
  
• If a task is updated to be 100% complete and the cost resource for the task is more than $83.33, the duration is reset unexpectedly.
  
• Consider the following scenario:
  • You have an enterprise calendar.
  • You set the enterprise calendar as the base calendar for some projects in the project server.
  • In preparation to delete the enterprise calendar, you go to the projects that are using the calendar and select a different calendar for them.
  • In Project Web App settings, you go to the Enterprise Calendars page and try to delete the calendar.
  In this situation, you can't delete the calendar because you are told that it is in use. After you install this update, you can now go to the projects in which the calendar is used, and use the organizer to delete it. After the calendar is deleted from the individual project that uses it, you will then be able to go to PWA and delete the calendar.
  
• Consider the following scenario:
  • You have a master project in which you have at least one sub project.
  • The master and sub projects have been saved to Project Server.
  • You unlink the sub project from the master project.
  • You save the sub project back to Project Server.
  In this situation, the assignments in the sub project are lost.
  
• Consider the following scenario:
  • You have a task in a project that has a resource assigned.
  • The resource assignment has 80h of work.
  • The resource assignment has split work wherein it works the first week, and it has a zero work split for the second week and finally has work on the last week.
  • The assignment is 50% complete and the first week is completed.
  On the Task Usage view, the actual work details of the assignment resembles the following: 
  8h, 8h, 8h, 8h, 8h, 0h, 0h, 0h, 0h, 0h
  You view the stop date and also notice that it's the same as the resume date. After you install the update, the trailing zero actual work values no longer appear and the stop date corresponds to where the last timephased actual work value that's more than zero is ended, and it's not the resume date which starts at the beginning of the third week.
  
• When you publish a project from Project 2016 to PWA, resource enterprise custom field values may be lost.
  
• When you publish a project to Project Server, formulas associated with a custom field that use the Current Date function will display the correct values. However, the published data for the same field may display a different value. For example, you have a custom task field with a formula that displays the current date. Then, you publish a project and you see the expected values on tasks in the custom field in PWA. Two days later, you open the same project in Project 2016, you see the correct values and publish the project. However, when you see the published values within the custom field in PWA, you see the same value from two days earlier.
  
• When status updates are applied, trailing timphased actual work values are created. This causes finish dates are later than expected.