Dynamics 365 Project Operations

Currently, project revenue postings are considered in the project statement only once they are invoiced.

Ideally, they are already considered as soon as they are posted.

For other project transactions (hours etc), the project statement includes them as soon as they are posted.

This idea is to propose that the expense management mobile app also displays the expense category name, for usability purposes.

Once expenses have been added to the mobile application, users only see the category icon and merchant value on the "Expenses" tab. When users create a new report and choose "Attach expenses", they only see the Merchant name (if this value was keyed in/selected when the expense was created). Even icons are not displayed on this form.

Not displaying the category name can create confusion for users as there are so few icons available and sometimes, the icons aren't shown.

When using the expense management app on my phone, all amount are wrong, they are multiplied by 100.

It seems like the app is missing support for multi cultural setup, i.e. where my user in Power Platform is using en-us as language, but my phone is using DK setup. This gives a difference in the decimal separator. this is common scenario and it makes the app useless if everything need to be fixed in FO afterwards.

So the change suggested here is for the app to support multicultural setup between the different devices.

To invoice for example a timesheet transaction with sales taxes in an intercompany customer invoice AND using there the standard function “Add line” will lead to a bug that the total amount from the intercompany customer invoice will differ from the automatic generated pending vendor invoice totals.

Problem is here that the sales taxes on line level in the intercompany customer invoice and also in the linked pending vendor invoice will be calculated wrongly if you have line number duplicates.

The idea would be to fix this standard behavior as you right now are not able to use the “Add Line” function on the intercompany customer invoice form.

In Project accounting, when you manage project budget with quantities, the quantity is not updated on the Budget Forecast Entity.

This means we cannot extract this information directly from the standard, and we need to customize by by retrieving this information from the table "ProjBudgetLineDetail".

This is clearly a discrepancy in the project budget database model.

when using the Expense Management app on your phone, it is only possible to add lines to expense reports, never to remove these again unless going into F&O.

Please add features to the app allowing users to remove lines from a draft expense report directly in the app and adding this expense to another report later.

The committed costs can only be generated for the whole company (by their type).

For performance reasons, it would be very useful to have a functionality to generate the committed costs for 1 project only (incl. subprojects). This would allow to have a button in the project form to re-generate only the committed costs of the project the customer is currently reviewing.

Currently, it is not even possible to extend the existing logic (all methods are private).

As organizations transition from Project Service Automation (PSA) to Project Operations (PO), they often encounter various errors that can disrupt the upgrade process. To streamline this transition and minimize downtime, it would be highly beneficial to have a comprehensive master list of potential errors, their root causes, and detailed steps to resolve them.

Benefits

• Reduced Downtime: Minimize disruptions during the upgrade process by proactively addressing common errors.
• Improved Efficiency: Streamline the upgrade process with clear guidelines and steps to resolve issues.
• Enhanced User Experience: Provide users with a smoother transition from PSA to PO, reducing frustration and increasing satisfaction.

Project journal reversed with the change funding source at project contract, system does not reverse the journal with the original funding source financial dimension. Due to this it causes the inconsistency for the reconciliation.

Please refer to Issue 886210