This article describes update KB3127994 for Microsoft Project 2016, which was released on December 6, 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?)
Consider the following scenario:
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
- Updates the translation of the check in confirm dialog box in Ukrainian when you close a changed project.
- Fixes the following issues:
- When you view a custom field lookup table within the Project Information dialog box, you may find that some expected values don't appear.
- When you open and save a Project 2003 project to a server, resource enterprise custom field values may be lost.
- Consider the following scenario:
- In a project, you go to the Resource Sheet view where you have resources defined.
- You insert one of the local Outline Code fields.
- From the outline code field on a resource or on resources, you select a value from the values that you have defined.
- You save the project to Project Server.
- Later, you set the outline code values to something else.
- You save, close and reopen the project.
- After you save a baseline, timephased work and cost values aren't displayed as expected. For example, you may see work and cost during periods where no work or cost exists.
- When you open certain XML files in Project, assignment delay is ignored. Therefore, the start and finish of some assignments on a task may be different. This can also cause the given task to schedule differently.
- In a master project, when you view the finish date of an inserted project summary task (this is the task that represents a subproject), you may find that it doesn't reflect the latest finish date of the tasks in the subproject.
- When you view a custom field lookup table within the Project Information dialog box, you may find that some expected values don't appear.
Consider the following scenario:
- You create a new report. For example, you create a new report that's based on the default Project Overview report.
- In a field list, you add more than one level of sorting.
- You save your project.
- You open your project.