Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
| Enabled for | Public preview | General availability |
|---|---|---|
| Users, automatically | 
Sep 27, 2024 |
Mar 31, 2025 |
Business value
Currently, in Dynamics 365 Project Operations, users see the markup cost only in actuals, based on the markup price configuration on a price list. The system doesn't show the markup cost in project estimates, quote line details (QLD), contract line details (CLD), or project budgets. This situation causes confusion because users see different prices in actuals when compared to estimates, QLD, CLD, and budgets.
Feature details
In the current implementation of Dynamics 365 Project Operations, the system limits visibility of the markup cost to the markup price configuration on a price list within the actuals.
Users see the markup cost in the actuals, but they don't see it in other critical areas such as project estimates, QLD, CLD, and project budgets.
This limitation causes confusion and inconsistency because the prices in the actuals differ from those in the estimates, QLD, CLD, and budgets.
This discrepancy causes misunderstandings and potential errors in project planning and financial tracking. The lack of visibility into the markup cost across all relevant sections creates a fragmented view of the project's financials.
Users can't accurately compare and reconcile the costs. This limitation creates challenges in maintaining a cohesive and transparent financial overview of projects.
With this release, the cost rate defaulting in project estimation scenarios respects and shows the markup cost across all estimates, QLD, CLD, and budgets.
Geographic areas
Visit the Explore Feature Geography report for Microsoft Azure areas where this feature is planned or available.
Language availability
Visit the Explore Feature Language report for information on this feature's availability.