Dynamics 365 Project Operations

Typically, resources are booked on projects well in advance, and they also request PTO / annual leave (AL) ahead of time.

Sometimes, a resource is already scheduled on a project for the same date they want to take AL.

On the Schedule Board, when a resource has 0 available hours due to PTO/AL, the system behaves inconsistently if the resource also has a project booking:

• Percentages break down:
• 0 ÷ 0 can show 0%, suggesting the resource is “free” (e.g., in weekly view).
• Booked hours against 0 availability can show >100% (e.g., 200%) in red, but it’s unclear which booking caused this. Expanding the resource record only shows the project booking, not the PTO/AL.
• Colors are misleading:
• Green may appear even when the resource is unavailable.
• Red appears for overbooking, but inconsistently depending on daily, weekly, or monthly aggregation.
• Views are inconsistent, causing confusion for dispatchers when trying to understand true availability.

Currently, the project contract can only either be in status Draft or Confirmed. Because after the contract is confirmed it can no longer be edited, Microsoft suggests to keep it in status Draft. That is misleading for Account managers and Project managers. Thefore, a new status should exist between Draft and Confirmed to signal that the project contract is complete, such as Ready or Qualified. If a new status is introduced, the Draft status should prevent invoicing.

Currently, there is no function to delete achievements, and there are no realistic plans to implement this function.

There is a restriction on achievements that prevents achievement data from being deleted from the system, and this is set to protect the integration with financial and accounting functions in project management.

As a result, this restriction cannot be lifted, and achievements cannot be deleted.

In addition, the project itself in which achievements exist cannot be deleted, and due to a design issue, there is no workaround.

However, a lot of data is stored during the course of work, and capacity is consumed every day.

For this reason, being able to delete unnecessary projects with registered achievements and achievements that are no longer necessary can free up some data capacity, and the ability to delete achievements is also convenient in terms of data management.

So, we hope that the function to delete achievements will be implemented.

If Sales prices for hours are invoiced without a full currency amount (e.g. 120,50) and no full hours (e.g. quarter hours and three-quarter hours), D365 rounds the decimal places at line level.

This can lead to differences in cents adding up in the total and an incorrect invoice amount being issued in relation to the sales price per hour.

Example: One hour has a sales price of $127.50. The service is invoiced with three items of 0.25 hours, 0.75 hours and 1 hour. The total of 2 hours is $255, but the individual lines are rounded up and the invoice amount is $255.01.

The more positions with 3 or more decimal places, the more the difference is added up. A manual change is not possible.

In connection with eInvoicing, which will be mandatory from 2025 in Germany for B2B-transactions, the check leads to the invoices not being accepted and rejected. It is not possible to change this logic with the rounding settings in the system.

The rounding rules must be adjusted in order to comply with legal requirements.

When using Porject Operations intensively, with many data conversions running and many batch processing jobs running, chances are, there will be some hick-ups in the process, possible causing corrupt data.

This, for instance now happened multiple times with one of our biggest customers, resulting in a request to Microsoft for disabling a plug-in that prevented us from doing a data correction.

The plug-in did not only prevent data in the table to be modified, but also had some functionality in it, filling certain fields in that table.

Disabling the plug-in had more effect than just enabling modifications. Also, requesting a plug-in to be disabled, takes a lot of time, and way too much effort, we sometimes needed multiple weeks, and multiple escalations to make it happen.

This idea has 2 changes in it :

Split up some plug-ins (for instance the one on the actuals table), so that it only enables or disables the modification of a record, and have all the other functionality in a different plug-in.

Enable the partner to disable or enable the plug-in that prevents the modification of a record, so there is no more dependency on Microsoft.

These 2 changes will make it much more easy for a parnter to correct data, and will cause higher partner satification but more importantly a better customer satisfaction.

The Consumed posting method in the Project accounting > Production parameters doesn't allow having a Costing sheet to be configured.

Therefore, there is no way to include surcharges such as Overhead as part of the cost for the item that is produced.

The alternative would be to configure Indirect cost components within the Project accounting module to add indirect cost when a specific type of transaction is posted.

However, Indirect cost components are not supported when direct Production order transactions are posted.

Suggestion: Add functionality that will create the Indirect cost amount in a posted Project transaction when the Production posting method is set to Consumed and the appropriate Cost category is posted within the Production order. If an Indirect cost is configured for that Cost category, it should create the indirect cost even though the Transaction origin is Production-consumed.

When creating a sales order from a Time & Material (T&M) project, the commission transaction is recorded with a settlement method of "On invoice", even though the Accounts receivable parameters are configured for "On payment". This behavior differs from what is observed when creating a standard (non-project) sales order.

Without it, users need to track the settlements of the invoices extra system, in order to pay commission to Agents.

Issue with mileage re-calculation in expense management when multiple reports are processed, however, when posted the total changes after posting.

This happens where there is an expense category with mileage tiers more than 1 setup. But if this category is created in all LE’s – then all LE’s would have this problem

This was not possible before the new functionality with the flight, it happened when we tested the flight.

Flight name: TrvExpMileageCalculationRevisedFlight

The impact is that when an employee/manager/accountant is a part of an expense process – the expense is calculated BUT it may change when posted. So, you can expect 1 amount to be paid but a different is paid.

In resource management on the Schedule Board, the booking method "Front Load Hours" is always automatically pre-selected during booking. This leads to incorrect calculations in our booking logic. "Evenly Distribute Hours" should be pre-selected or only available as the sole booking method for us. When booking resources, it must be remembered to change the booking method to "Evenly Distribute Hours." If you change the booking method and then enter the resource (name), the selected booking method changes back from "Evenly Distribute Hours" to "Front Load Hours." These two scenarios cause problems in our resource management because we always plan based on the even distribution of hours over the period.

It would be great to be able to save a personal view with the applied "group by" option. So that I do not have to apply the "group by" again everytime I want to get an overview via my personal view.

This would reduce the amount of clicks and makes the usage of personal views more efficient.