This security update contains improvements and fixes for the following nonsecurity issues:
- When you make changes in a project and then save it, the custom field lookup table values are also saved even though they have not been changed. Therefore, it takes longer to publish the project. And while the publishing processes, other actions such as viewing the tasks view in Project Web App may be slow.
- Assume that you update cost or work data for a subtask in Project 2016. When you save a baseline on the task and choose the option to roll up the baseline data to all summary tasks, the baseline data for task summary tasks within the sub project is rolled up but not to the inserted project summary tasks and summary tasks in the master project.
Consider the following scenario:
- You have a SharePoint document library.
- The document library list experience is set to the new "modern" experience.
- The document library versioning settings require checkout.
- You have a Project file stored in the library. You open the file from the library by using Project 2016.
In this situation, you find that the expected "check out required" prompt isn't displayed, and therefore you can't respond. This means that if you make changes to the project and save, Project tells you that the changes can't be saved because checkout is required.