Applies to Product - Dynamics 365 Project Operations
What’s happening?
The issue involves the loss of data when creating a new child Work Breakdown Structure (WBS) if the parent WBS contains cost data in the Cost estimate view.
Reason:
The loss of cost data occurs because, by design, when a task is indented under another task, the parent task becomes a summary task. As a result, it loses its own dates, effort, number of resources, and cost estimate, instead using a summary of the values of its new constituent tasks.
Resolution:
The parent task is a summary or container tasks. A summary task is a task that has sub-tasks or constituent tasks beneath it. A summary task doesn’t have any work effort or cost of its own. Instead, the work effort and cost of a summary task are the sum of the work effort and cost of its constituent tasks. The earliest start date of the constituent tasks is used as the start date of the summary task, and the latest end date of the constituent tasks is used as the end date. You can modify the name of a summary task, but you can’t modify the scheduling properties for effort, dates, and duration. If you delete a summary task, you also delete all its constituent tasks.
When you create a new child WBS task:
- Assign cost estimates to the new child WBS ID.
- Confirm that parent WBS cost estimates are allocated to Child WBS IDs so that parent WBS shows total estimated cost correctly.
- For further details, refer to the documentation on Work Breakdown Structures available at the provided Microsoft documentation link.