Dynamics 365 Project Operations

When an asset has been created from the Project management and accounting module and additional cost to add life to the asset are incurred in a sub project then D365/AX can only posts these costs as a new 'acquisition'. There is no possibility to select a different posting type such as acquisition adjustment or write up journal, etc.

Please make a corresponding enhancement with the next release.

Thank you and best regards,

Stacy Black

Working with item requirements is not allowed if multiple funding sources are setup in the project contract that is attached to the project.

It would be very helpfull if a design change was made which allowed working with item requirements and/or project sales orders in conjunction with a project contract with multiple funding sources.

A recent update based on KB3178570 made it impossible to change the project contract after project transactions were made. This was done to prevent a problem in a specific scenario. However, this also caused a regression in functionality.

All information from the project contract is stored in the project transactions, including the funding source. To that end changing the project contract on a running project should be possible. This allows users to change the customer (and other commercial details) of a running project for all new transactions. In the meanwhile the existing transactions can be invoiced based on the old project contract.

This functionality is even more needed since a funding source cannot be change while project transactions exist (which is good) and working with multiple funding sources is not allowed when working with item requirement and/or project salesorders.

There should be line discounts on project item transactions and project invoice in order to invoice items with use of projects item transactions. You often invoice item transactions which originate from project item journals and project purchase orders instead of using a project sales order.

You have trade agreements with discounts, and use for example both retail/sales orders and projects to deliver/invoice items to the customers. But since discounts are not fully supported in project module, then you need extra manual work to support both scenarios.

As-is there are discount fields on some project business documents, but you need discount fully implemented on all documents in order do fully support discounts in same way as using standard sales order, including transfer from project quotation to project. For example there are now no discount on item requirement, WBS, project invoice report, project adjustment etc.

There are also different behaviour when discount is used as-is, either the net amount is reduced with discount or the unit sales price is reduced with discount on the project item transactions. It should be consistent with net amount reduced with discount, with discount field in addition as on sales order. I have submitted this to Microsoft and it has been postponed - LCS link: https://fix.lcs.dynamics.com/Issue/NotFixed/1187145?bugId=3838627&qc=80d1139efec6e5968deca0fc4bae275f16a19c67ad29f3682eafb8d8f3ceeec2

Create data entity for Estimate Projects (ProjWIPTable).  Without this data entity, the necessary estimate project cannot be loaded and associated for Fixed-Price projects through data migration.