Currently in the system we have our default project calculation preferences set to Manual. Prior to the Paris upgrade, we were able to update task planned dates with no issues. Post Paris Upgrade, we noticed an error occurring when making updates in the Planning Console (see below). As a work around, our tech team advised updating the calculation preferences to Automatic on all projects, OR using the project list view to update the project tasks. We are seeking clarification between Automatic and Manual preferences and how the Planning Console is effected, but the list view is not. We are also needing a better understanding around how each of the calculations preferences update the percent complete column and which of the two (automatic or manual) is preferred to avoid needing to update the percent complete field manually at a task level.
Hello,
In Paris, a new field was introduced to the Project and Project task table, the Constraint date field. The read-only Constraint date field has been added to the Project form to help you better understand how the start date is calculated for project tasks. For example, the date in this field is used to calculate the start date for tasks with the Start ASAP constraint.
The Constraint date field is used for time constraint and conflict calculations between the Project and Project tasks on the Project task.
| Constraint date | A read-only field that displays the project's planned start date. The date in this field is used for calculate the start date of the tasks with Start ASAP constraint.
Use the Move Project related link to change the constraint date. Changing this date also changes the start date for all the tasks with Start ASAP constraint. For more information, see Change the planned start date of a project. |
What that out of the way. Here where it gets tricky and why you might be getting that error message.
In Project Task, the "Planned start date" is controlled by the Project Task's Time Constraint field. Suppose the Project calculation field is set to Manual. The Project Task's Time Constraint will always get set to "Start on specific date" and is not editable and set to read-only. The "Start on specific date" option does allow for the Planned start date to be editable. However, it is only editable if the state is open or pending. If the project task's child tasks are rolled up, this will also make the planned start date read-only. Changing the start date also changes the "Constraint date."
If the Project calculation field is set to Automatic, by default, the Project Task's Time Constraint is set to "Start ASAP. The Planned Start date is auto-populated from the Project's Planned Start date and is set to read-only; however, it will not populate the "Constraint date." This happens a lot in the Planning console because the Project Task's Time Constraint isn't as visible as is in the detail page, making it easy to skip over.
You also can change the Project Task's Time Constraint because it is not set to read-only. You have three options - "Start on specific date," Start no earlier than," and "start not later than."All those choices give you the ability to edit the Planned start date. The same rules apply to changing the Planned Start date - it is only editable if the state is open or pending. If the project task's child tasks are rolled up, this will also make the time Constraint read-only. Changing the start date also changes the "Constraint date."
As far as this statement - update the percent complete column and which of the two (automatic or manual) is preferred to avoid needing to update the percent complete field manually at a task level.
Can you explain this some more?
Also, can you tell me what you did to get that error message?
I added some documentation to help you understand this some more.
Here is ServiceNow's definition for the Project Constraint date field
The Constraint date field on the Project task
Time constraints in parent-child relationships
