2
In AX2012 this was working correctly meaning it was possible to change the dates of a task without having automatically changed the dates of the other (successor) tasks.
The scheduling error was shown, stating the discrepancies or time lags in the dates, but it was possible to decide whether to fix them or not.
This is in line with the usually business process as you need to first check the availability of the resources for the other task, prior moving the dates.
D365 automatically moves all dates which can cause resource overbookings or misalignment with the actual project progress.
Feedback from engineering team is that the design of Dynamics 365 work in the following way: Setting predecessor and successor will have the successor to start date as predecessor finish date + 1.
If you have predecessor and successor in D365 the dates will always be +1 and the gap cannot be much bigger.
However, user would like to have the option as in AX2012: to be possible to change the dates of a task without having automatically changed the dates of the other (successor) tasks.
The scheduling error was shown, stating the discrepancies or time lags in the dates, but it was possible to decide whether to fix them or not.
This is in line with the usually business process as you need to first check the availability of the resources for the other task, prior moving the dates.
D365 automatically moves all dates which can cause resource overbookings or misalignment with the actual project progress.
Feedback from engineering team is that the design of Dynamics 365 work in the following way: Setting predecessor and successor will have the successor to start date as predecessor finish date + 1.
If you have predecessor and successor in D365 the dates will always be +1 and the gap cannot be much bigger.
However, user would like to have the option as in AX2012: to be possible to change the dates of a task without having automatically changed the dates of the other (successor) tasks.
STATUS DETAILS
New