Can you prevent tasks in subprojects from being updated when a master project is Autoscheduled?
Release: 16.0.1
Component: ODPRM
There are multiple ways to prevent the entire subproject from being rescheduled or selected tasks within the subprojects.
To prevent a subproject's tasks from changing in a tentative schedule is to lock the tasks by one of the below methods:
Locking tasks directly prevent them from being auto-scheduled in any situation.
Locking tasks directly prevent them from being auto-scheduled in any situation.
The ability to use Autoschedule in Modern UX for Projects has been introduced in Release 16.0.1
When auto-scheduling a master project in Gantt with a subproject set as read-only, you get the following alert:
The following subprojects are already locked, marked read-only, or you don't have rights to change them. If you create a tentative schedule now, changes to the tentative schedule for those subprojects will not be able to be published back to the plan of record. Do you still want to continue?
If you decide to continue along with the auto-scheduling action, Gantt will show the new proposed dates and while the tentative schedule is on Clarity will also move the dates accordingly.
However, at publishing time, as the alert states, the changes will not be saved and the dates will be reverted back to the original state.
Even if the behavior might look confusing, the alert was introduced to get users aware of it