Dynamics 365 Project Operations

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.

Create a parent project and a Subproject. Same Project group but different dimensions. 

Register a cost for parent project.

Adjust the transaction, to move cost from Parent Project to Subproject. 

GL records incorrectly, original entry is not reversed.  

Expectation: the original entry should have been reversed, the correct accounting with proper dimensions to be created and post to subproject.

Support for advances and retainers on subcontracts

Be able to trigger the print management of FO to communicate the purchase order confirmation. Verdord need the purchase order number from FO to make their invoice with our purchase order number so it can be matched automatically.

Today the project cash flow only includes the opening balance for the cost, not the opening balance for the on-account.

This makes the cash flow not correct.

It should either include both on-acccount and costs from opening balance or neither of them should be included.

I think the best solution should be to include both.

When editing bookings for which span over several weeks or months. We would like to set a particular period to 0 hours which would cancel out those bookings for that time frame.

Currently the lowest we can set it to is 1 hour which is not ideal.

Example - 'https://imgur.com/a/1B77hsg'

Clients often times have a pool of resources who can complete a task. There needs to be a way to allow a group or team to be assigned to a task. D365 Field Service has the concept of Bookable Resource Type = Pool. Can this be made availabe in D365 Project Operations?

On large enterprise projects, many tasks can require supporting documentation to demonstrate completion of the task. Integration with SharePoint for document management should match the WBS hierarchy, to allow for a good user experience. For example, task 1.1 should have a corresponding folder 1.1, 1.2 should have a corresponding folder etc. Addtionally, task ownership and Dataverse security should also map to SharePoint, to a provide a clean and scalable user experience.

I am pretty pleased with the app's functionality, but there should be one improvement. The app should allow us to relabel or rename a receipt when it is added. When receipts are saved to the system, they may not necessarily go to an expense right away. It would be nice to be able to label them with the merchant or amount so that when I assign them to an expense, without having to open each receipt. The functionality was available on the retired F&O app.

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.