Dynamics Community Forum Thread Details

End task auto updates.

Hi,

I have a client on D365 Project operations who is expecting to see a change in the task end date on a project when the Actual time taken to complete the task is differs from the estimated effort.

Scenario: I have a project with task 'Configuration' with Start date setup as 9th Feb, 2026 and End date setup as 13th Feb, 2026. Duration for this task is 40 hours (i.e 8 hours * 5 days). The resource who has been assigned this task does not complete it on 13th Feb, 2026 as planned. The resource enters 8 hours * 5 during the week 9th to 13th Feb. Since the task isn't complete yet, the resource adds an extra 8 hours the following Monday i.e. on 16th Feb 2026.

Will the Finish date automatically move to 16th Feb 2026 for this task?

I have tried with all the Schedule modes and I don't see the Finish date getting updated automatically.

Is this possible in D365 Project operations at all? If yes, is there any setup for this feature to work.

Thanks,

Categories:

Dynamics 365 Project Operations

Hi PD-20020856-0

1) Issue
- In D365 Project Operations the task finish date does not update automatically based on actual effort entered
- A task planned from 09 Feb to 13 Feb (40 hours) remains unchanged even after additional actual hours are entered on 16 Feb
- Users expect the task end date to extend automatically when actual time exceeds the planned duration
- This behavior is observed across different scheduling modes

2) Reason
- The behavior is caused by the design of the Project scheduling engine in D365 Project Operations
- Actual hours entered through time entries do not directly drive task scheduling updates
- Task scheduling (start/end dates, duration) is controlled by the scheduling engine (Project for the Web / scheduling service), not by actuals

This leads to a separation between:
- Effort tracking (actuals via time entries)
- Schedule management (task dates and duration)

- This means that entering additional hours does not automatically extend the schedule because the system does not interpret actuals as a trigger for rescheduling
- This can happen because Project Operations follows a planning-first model where schedule updates must be explicitly triggered or managed through task updates, not inferred from time entries
- Even in auto-scheduled mode, the engine recalculates based on dependencies and duration changes, not actual effort directly

3) Resolution
- Understand standard system behavior
- Task dates will not automatically move based on time entry or actual effort
- Additional work must be reflected manually or through schedule updates

Option 1 (Standard approach)
- Manually update the task:
- Extend duration or effort
- Update end date explicitly to reflect reality
- The scheduling engine will then recalculate dependent tasks

Option 2 (Recommended planning approach)
- Use % Complete or Remaining effort fields

Update the task:
- Increase remaining duration/effort when work exceeds plan
- The scheduling engine will adjust dates accordingly

Option 3 (Using dependencies)
- If tasks are linked, changing duration will automatically shift successor tasks
- Ensure dependencies are correctly configured so schedule recalculates

Option 4 (Project for the Web integration)
- Open the project in Project (schedule board)
- Adjust effort or duration there
- Save changes so schedule is recalculated centrally

Option 5 (Customization)
- Implement automation using Power Automate or plugin:
- Detect when actual effort exceeds planned effort
- Automatically update task duration/end date
- Warning: This requires careful handling to avoid schedule inconsistencies

Option 6 (Best practice)
- Track overruns using:
- Effort variance
- Schedule variance
- Do not rely on automatic schedule correction based on actuals

Key takeaway
- D365 Project Operations does NOT support automatic extension of task end date based on actual hours
- Schedule and actuals are intentionally decoupled
- To reflect delays, the task schedule must be updated explicitly or via controlled automation

For a more detailed answer, please provide more information.

Rg,

Alexander

*Due to the complex and different possibilities of deploying Dynamics 365 I highly recommend not to setup the application without some expert/partner or support. (For more information contact me under anassl@inno-solutions.info or visit www.inno-solutions.de)

*The Information comes directly from the manufacturer or provider and are validated (not guaranteed) up to date of creation of the posting.

References: