Work hour templates are based on a bookable resource's work hours, but they don't have a calendar tab. To view or edit these templates, you need to go to the resource and update their work hours. Similarly, if the work hours in the templates change, you must check the resource's calendar to see those changes.

To make it easier to update the work hour template, we plan to add a calendar tab within the work hour template entity.

Currently, to bring tasks from another project into a new project, users must manually enter the task details in the task grid or use schedule APIs. They can also use the copy project feature to create a new project with the same tasks, but this has limitations:

• The entire project is copied, including unwanted tasks and extra information.
• Tasks from multiple projects cannot be combined into a new project.

This new feature allows users to select and import tasks from one or more existing projects into a new project, saving time and effort. Users can choose the project and tasks to import while adhering to the task limits per project as specified in the public documentation.

Project and project task start and end are saved in a date-time format that is converted to GMT prior to saving. They are then converted back to the user's time zone when being displayed in the product. However, some integrations and customizations pull only the date from this field. Problems with this arise when the conversion to GMT changes the date, then an integration pulls only that date from the field without converting it back to GMT.

To prevent this, new fields on the entity are being created to store the start and end date time without first converting to GMT. This allows you to confidently pull only the date without concern that the time-zone conversion has caused the date to change.

In Revenue recognition, Fixed price billing arrangements are used along with billing milestones to set the contract value. Customers have a need for a separate calculation for the contract value from the billing milestones when additional effort or resources may be required to complete a fixed price project or when a contract line is discounted.

The contract value is used for calculating revenue recognition while billing milestones are used to invoice the customer. Separating these values allows users to recognize revenue based on the effort or stand-alone selling price aligning better with ASC 606 and IFRS 15 requirements.

Copy project functionality is available for customers who use the default scheduling engine, but not for externally scheduled projects. This new feature adds copy project functionality for externally scheduled projects, allowing the project entity in Microsoft Dataverse to be copied to a new project.

The feature offers you the ability to customize Billing hub at all levels of the nested grid, including contract, contract line, and contract line views. The feature is automatically enabled for admins so you can customize Billing hub forms and views to fit your organization's needs. For example, with this update you'll be able to add more columns like Invoice ID to the contract view or add Discount % and Fee % to your contract line view in Billing hub.

The following fixes are included in this release:

• Platform bug fix for Grid customizer, making contract level customization feasible.
• Ability to customize views on Contract lines for time, material, expense, fee, and milestones.

In the task grid, when you select the (i) icon next to a task name, the Task details pane opens so you can enter more information. This pane is part of Microsoft Project for the web and is embedded in an iframe that makes it non-customizable.

With this new feature, we plan to introduce a customizable Task form. This form will display essential task attributes and allow users to view and edit custom columns. This will enable customers to manage and track project tasks more easily in one place. .

By enabling this capability, users will be able to:

• Manually edit the transaction date for per-diem expenses.
• Manually update the exchange rate to be used for currency conversion.

The modified information will be used in subsequent expense-related calculations and postings.

The feature will be released behind a feature flag or as a parameter within the expense management parameters page.

This feature consolidates cost and sales visibility into a single, easily accessible One Grid view while maintaining control over editable fields, thus improving efficiency, accuracy, and user satisfaction in managing estimates.

Previously, there were limited options to determine how financial dimensions default. This feature adds functionality and more flexibility in defaulting financial dimension values. With this feature, you can:

• Create a configuration to determine how financial dimensions default based on criteria like contract, project, or cost and revenue profile.
• Set criteria to determine if dimensions should default from contract lines or projects.
• Improve reliability when saving financial dimensions and value defaults on the project.
• Add the ability to set dimensions on time and material contract lines.
• Add the ability to use contract lines for revenue recognition.

In the example in the image below, the system uses the following logic:

• The line at the bottom of the grid defaults all projects and contracts to use the project dimension unless an individual record overrides that behavior.
• The table line at the top of the grid is the next most specific record and causes all projects associated with contract 00000017 to use the dimensions from the project.
• The middle line is the most specific record because it is project-specific, it overrides previously defined behavior, and has all transactions specific to Project 000000004 use the contract line for the basis of default dimensions.

The Enable contract line based revenue recognition with Project Operations for non-stocked/resource based scenarios feature modifies the Project default dimension rules form by adding another column to add rules based on specific contract line groups as the first filter.

Ensuring that the milestone date (invoice date) is consistently displayed across both the project contract line milestone entity and the invoice entity will help by improving:

• Accuracy of Invoicing of fixed price contract lines, thereby ensuring consistency of milestone date between both project contract line and invoice, ensuring fewer corrections downstream.
• Efficiency of the invoicing process, thereby reducing the administrative burden and allowing finance teams to operate more efficiently. This can lead to faster cash flow and improved financial management.

The feature will introduce a new tab on the expense management parameters page, allowing users to assign number sequences directly. The process of configuring number sequences will align with the experience in other modules of the application, making it more intuitive. This enhancement enables users to manage number sequences within the module itself, rather than having to access and modify the number sequence master.

With this feature, the correct sales and cost prices will be automatically updated in quotes and contracts based on date effectivity. Prices will be computed using weighted average prices for both quote line details and contract line details, ensuring precise and reliable pricing calculations. This automation significantly reduces the manual effort previously required to track and update prices, minimizing the risk of errors and discrepancies in pricing.

Additionally, the new feature includes the ability to maintain a comprehensive audit trail of all changes made to quotes and contracts. This allows for full transparency and traceability, giving users confidence in the accuracy and integrity of their pricing information.

Users will now have the ability to see exact totals at any point in time, reflecting all current and historical pricing data. This real-time visibility into totals enhances contract management and helps ensure that all financial aspects are accurately accounted for.

This feature implements a security system that allows administrators to set restrictions on what a user can access inside the Project for the web iFrame on projects for which they have access to but are not team members. Additionally, we will implement the same system for project managers to set these restrictions for team members on their projects.

Previously, importing from an MPP file would create a new project, copying the WBS from the MPP file to the new project. It wasn't possible to import into an existing project. This made it difficult when overall planning was done in Project Operations and individual planning was done offline in Microsoft Project for desktop.

This feature allows users to import MPP files into existing projects to keep overall planning intact. It aligns with the Copy project feature but uses an MPP file for importing.

Users can:

• Set calendar hours (existing capability)
• Set the project manager (existing capability)
• Set schedule mode if override is allowed (existing capability)
• Select the source MPP file (existing capability)
• Select the target project (new capability)
• Choose what to import from the MPP file (new capability)

This feature will be implemented in phases. In phase 1, we are increasing the limits for:

• Number of tasks per project.
• Number of assignments per task.
• Number of assignments per project.

In phase 2, we plan to enhance overall performance after increasing these limits to reduce performance-related tickets and boost customer satisfaction with Project Operations.

This feature combines the capabilities of both V3 and V4 into a single, user-friendly interface. Users can copy projects according to their needs.

On the user interface, users can select:

• Source Project
• Target Project
• Team Member Mapping:
  • Don't copy team members
  • Replace team members with generic team members
  • Copy the named/generic team members as in the source project

The feature will provide administrators with a parameter on the Expense Management Parameters page. When this parameter is enabled, expenses are posted based on the posting date instead of the transaction date.

This feature helps you:

• Establish relationships between sales categories and procurement categories.
• Enable item requirements for procurement categories.
• Automatically post item requirements packing slips during the receipt of purchase order products.
• Create project invoices to customers with sales prices automatically calculated during the purchase product receipt.

Some Project Operations customers don't use time entries to track their progress on tasks. For these customers, there are challenges in completing tasks because that requires time entries to increase the Completed state for the effort. With this update, we're adding functionality to mark a task as complete from the grid view, the way Project for the web does by default.

This feature aims to improve the usability of invoice editing. The changes include:

• Reduced clicks to edit one or more invoice line details.
• Reduced clicks to bulk-edit multiple fields on an invoice line detail.

Additionally, it will provide billing administrators with an improved invoice summary that provides key invoice insights to enable faster decision making.

Key enhancements in this feature include:

• Inclusion of workflow history
• Ability to map expenses to a travel requisition
• Quick matching of expenses with receipts
• Ability to add interim and final approver
• Ability to merge/match expenses
• Ability for expense submitters to attest anti-corruption

These enhancements will be released behind a feature flag, Expense Reports Re-Imagined Enhancements, and will require the Expense Reports Re-Imagined feature to be enabled first.

Project Operations lets you define discount percentages and fee percentages at the level of the project quotation or the contract line. When a transaction is generated and approved, the system applies the appropriate discount or fee, based on the contract line setup. Then the system updates the actuals accordingly. During the invoicing process, discounts and fee amounts, if applicable, are applied and financial transactions will be generated accordingly.

Customers can assign delivery addresses on project contracts and funding sources. These addresses will be defaulted on the project invoices and synchronized with Dynamics 365 Finance for project invoices.

Financial tags that are defined within the general ledger are stored on accounting entries posted to the general ledger. The financial tag names can be defined by the user, giving clarity to data entry clerks about the data expected in each field. Financial tag values are not validated or entered by default. Tags are entered on the journals and flow through to the invoice.

For this release, we are adding tags in many of the common project accounting documents and processes. Project journals and sales orders are the first documents with added support. Tags flow through from document posting to invoicing.

We have received requests for the ability to use journals in Dynamics 365 Finance against resource and non-stocked projects. This feature relaxes restrictions and allows for expense type general journals to be created and flow through to Dataverse. New capabilities include:

• Using the resource/non-stocked deployment, you'll be able to select Project as the source or the offset for the journal, with Ledger being the other side of the transaction.
• Journals created in Finance will integrate and flow back into Dataverse. Within Dataverse, actuals will be created against the project.
• A new posting approach will be implemented for this document that eliminates the use of the expense integration account.

Some of the most commonly used business processes that project managers perform during subcontract management include:

• Modify subcontract line
• Track subcontract usage
• Monitor billing progress for subcontracts

Currently, project managers need to navigate through multiple forms and interfaces to use these business processes. This complexity increases when managing vendors and subcontracts across various projects.

The upcoming feature enhancement will streamline this process, allowing project managers to handle these tasks more efficiently.

This feature will be enabled behind a feature flag to ensure that customers and partners can adapt to the changes on top of any customizations they might have added.

A new workspace has been introduced for the resource/nonstocked deployment type of Dynamics 365 Project Operations. This workspace enables new scenarios to save time troubleshooting errors and reviewing configuration errors, system errors, and other potential issues that otherwise would be buried in logs or missed.

For example, the workspace enables customers to identify and resolve dual-write sync issues specifically related to vendor invoices and expenses. It provides detailed insights into the root causes of errors, including the number of affected records and associated amounts, ensuring a clear understanding of the scope of the issue.

New capabilities include:

• A new dashboard supporting accountants by highlighting pending journal postings and integration journal lines that have not been created, as well as any missing records, facilitating efficient ledger reconciliation.
• A new batch process to resync data, allowing users to address and resolve issues effectively, ensuring data consistency and operational continuity.
• A detailed view of several documents such as expense reports and vendor invoices indicating if they are in sync between Dataverse and the finance and operations infrastructure.
• A troubleshooting view where the full logs of the integration journal and invoice proposals are available and aren't truncated.

This feature brings together the new grid support into Project's expense and material estimate grids. Today these custom grids are not performant and lack extensibility and capabilities. This feature enables the capabilities of the new modern grid to improve the overall experience for its users.

These enhancements include:

• Improved grid with a view switcher.
• Improved grid allowing extensibility.
• Task sorting by work breakdown structure.
• Quick create experience to easily add expense and material estimates.

The experiences for using inventoried products in Projects Operations will use the Inventory and Warehouse modules of Dynamics 365 Supply Chain Management. Pricing and Inventory visibility services are used to accurately estimate the availability of stocked items and their costs. The Inventory close process in Supply Chain Management will be used to update project cost to reflect accurate consumption of project budgets. This will be a multiple release wave effort to fully light up all the capabilities needed to manage stocked items on projects.

This feature introduces enhancements to improve the management of quotes. Users can add or edit quote line details directly from a unified grid interface, with cost details accessible. The feature provides various insightful details such as customer schedules, margins, and budgets in the quote line detail, and allows seamless addition of new lines.

These improvements streamline quote management to enhance functionality, accuracy, and efficiency.

The feature will be available to users in Early Access Update 1. At the beginning of 2025 release wave 1, the feature will be generally available to use.

The enhancements introduced with this feature work toward parallel use of projects from both deployment types. This change allows for limited transaction entry and invoicing for long-running projects in support of moving fully to the modern architecture. This is a large effort that won't have all functionality delivered at once. The enhancements will allow customers to try the modern architecture in a test environment, and move from the stocked deployment type to resource/non-stocked deployment type if desired.

This feature is for customers who are using our stocked/production order deployment type without the need for production orders or manufacturing. The changes made allow customers who have used the Project Management and Accounting module in the past to now enable the resource/non-stocked deployment type without having to reimplement their existing legal entity. Customers who want to continue using the capabilities in the stocked deployment type won't be impacted by any changes made in this feature.

Changes include:

• The existing validation in the Global project management and accounting parameters form will be relaxed to allow legal entities with existing project data to be enabled for resource/non-stock deployment types.

• The Global project management and accounting parameters validation will now check for all projects to be closed. The initial requirements for this feature will be to support closing all existing projects and creating new projects within Dataverse going forward.

• Business processes will be evaluated to ensure proper restrictions are in place for the appropriate deployment types. For example, invoices for Dataverse-based projects can only be created from Dataverse.

• We will remove access or make read-only the legacy functions that exist in both deployment types. For example, resource management and project work breakdown structures will no longer be editable in the finance and operations user interface for the resource/non-stocked deployment mode with this feature enabled. For projects created in resource/non-stocked deployment mode, users are able to use Unified Resource Scheduling experiences for resource scheduling, and Project for the Web experiences for project planning.

The web experience for time entry in Dynamics 365 Project Operations is receiving a series of improvements to facilitate faster, more accurate time entry, with better overall tracking for team members.

These upgrades include:

• A new Calendar interface to view, create, and modify time entries.
• The ability to track time logged across varying timelines (weekly, monthly, and so on).
• Tighter integration of work breakdown structure (for assigned tasks and projects) within the time entry creation step (Quick create forms).
• Improved tracking in the form of benchmarking (Actuals vs. Target hours) and visualizations to help team members track their progress on project tasks.

Project team members on Lite and resource/nonstocked-based deployments of Project Operations now have a new mobile application based on Microsoft Power Apps. The new mobile app helps them log time, keep track of submitted entries, and view the work assigned to them.

The application provides users with the following capabilities:

• A view that summarizes all Microsoft Outlook meetings and Microsoft to-do items for that day. These meetings and to-do items can then directly be used to log time entries.
• The ability to view projects and tasks on which the team member is currently staffed, and the duration that the staffed project is going to run for.
• A section to view day-wise time entries, across statuses (Draft, Submitted, and so on) where users can modify or delete editable entries, submit entries for approval or recall already submitted entries.
• Users now get access to a new mode of logging time with the help of a timer that can be used to record the duration of granular work performed, and then later be tagged to a project or task and turned into a time entry.

All changes made on the mobile app will be synced to the web app for Project Operations or Project Operations Team Member and vice versa. Steps to install or enable this mobile app will be updated soon.

The Approvals feature will get an overhaul of the UI experience for approvals in Project Operations. These UI changes include showing approvals in a calendar grid, like the Time entry creation grid, and highlighting the most relevant information so project managers can easily see which records need their attention.

The functionality of start and end dates in projects and project tasks within Dynamics 365 Project Operations entails the inclusion of supplementary fields that aren't dependent on specific time zones. These additional fields are incorporated into both the project and project task entities, thereby facilitating integration and extensibility possibilities for scenarios where the time zone aspect of the start and end fields is not of utmost importance or for improved accounting alignment.

Time zone-agnostic fields on resource requirements and resource bookings allow project owners to set the default start and end dates for a project’s resource requirements, details, bookings, and related tables.

Currently, all date fields in these entities are time zone-aware and convert the dates when users are based in different time zones from when the requirements and bookings were created. This conversion results in unintentional discrepancies. This feature aims to enhance extensibility by providing flexibility for organizations to use time zone-independent date fields when their organization spans across multiple geographies.