Dynamics 365 Project Operations

When enabling the "Project invoice proposal performance enhancement feature" in the "Project management and accounting parameters" a new setup for "Invoice"

"Display available transactions automatically" is available to set the default value.

But in the "Project invoice proposals" when creating a new proposal the "Display available transactions automatically" is greyed out.

For single invoice automatically would be fine.

But for a collective invoice, many filters has to be entered. And for every field the system automatically try to display the result. But this takes several minutes.

The best would be, when the "Display available transactions automatically" would not be greyed out in the create invoices proposal form.

Workaround: "Project invoice proposal performance enhancement feature" disabled

When a user is doing an adjustment in the project to change the line property or price, it is not allowed to proceed to the item that does not have an on-hand inventory.

We should be able to adjust items/change without needing stock on hand for items we have already consumed/posted.

Scenario: You have a customer with an separate invoice account on the customer record.

The same customer is setup on a project contract.

When invoicing the project and creating the project invoice proposal and selecting the project contract. The invoice account from the customer record is selected instead of the customer on the project contract funding source.

A workaround is to create two customer records for the same customer (one with invoice account and one without).

The funding source on the project contract have to be the customer account without an invoice account.

This workaround generates tremendous numbers of customer accounts.

It should be possible to select when generating a project invoice proposal whether the funding source or invoice account is the receiver of the invoice.

Currently there is no such a feature to edit [Schedule section] in [Project] of [Project Operations app].

If this section is editable, it would be very user-friendly.

In Microsoft Dynamics Project Operations, when a custom attribute is added to the task grid, its default value is not automatically applied to new records. This issue occurs even though the default value is correctly configured in the attribute settings. Interestingly, the behavior appears to be linked to the visibility of the column: when the custom attribute column is added to the task grid, the default value is not populated; however, when the column is removed, the default value is applied as expected. This suggests a potential bug or limitation in how the task grid handles default values for custom fields.

We received feedback from our customer that it would be helpful for users to receive a warning when the same field is updated by another user in parallel as it is the case in F&O. For example, if the customer in a project changes and another user changes it in parallel, the user should receive a warning message that says (similar to F&O): "The record shown has been updated by another user."

The advantage would be that updates by any users would not have the risk of overwriting values that are (already) changed by another user at the same time.

F+O workflows for Project Budgets, PO Approvals etc. are limited to a small set of fields to be used as workflow conditions e.g. Project ID. All of which can not be delineated in the Project module to indicate the nature or type of Project which can be a required in respect to who and what approvals are required. E.g. a capital project may have additional approval steps / controls compared to an internal project.

As there is only 1 Project ID number sequence, this field can not be utilized as a workflow condition to dictate workflow branches based on the nature of the Project. The only viable work arounds are to either have a manual Project ID number sequence and inform users of Project ID naming conventions which they will need to enforce on their own or create a Project Group financial dimension.

In respect to the Project Group financial dimension, this is not an ideal candidate for a financial dimension segment as we can dictate postings based on Project Groups and have dedicated accounts for capital v. internal v. revenue etc.

Idea: Utilize the same functionality / logic as Fixed Groups to allow for the definition of unique number sequences by Project Group. This would both enable the use of Project ID in workflow configurations beyond simply 'Is Project? condition' and eliminate the need for customers to create a Project Group financial dimension simply to add improved workflow capabilities.

Alternatively - Add the Project Type field into Project Budget and Purchase / Sales Order workflows

Currently, project tasks are managed by checking whether the completed work time exceeds the total work time.

For example, there is no feature to check whether a task is complete even if the completed work time is less than the planned time.

By implementing a feature to check whether a task is complete or incomplete, regardless of the completed work time, users will be able to manage their tasks more accurately.

We would like to have a field that allows us to see how many hours a task was planned for at the time of order receipt, and to see how much difference there was during and at the end of the project.

However, the Project Task Grid in Project Operations does not allow the addition of custom columns because it is the item used to manage the Work Breakdown Schematic (WBS) in iFrame, which is hosted within Microsoft Dataverse.

We would like the ability to add custom columns to achieve the desired behavior.

Currently, it is necessary to have Project Operations integration enabled in an entity to import a Project Contract header or other relevant data.

It is necessary for the Legal Entity to not have any data to be able to enable this feature, which leads to a dead-end in which you may need to import data but cannot do it due to the lack of integrated legal entity. At the same time, you are unable to integrate the entity because it already has a project on it.

It is true that the public documentation informs of this limitation, but we would still request to have an option to allow this feature on legal entities with data on them.

https://learn.microsoft.com/en-us/dynamics365/project-operations/environment/resource-configure-integration-per-legal-entity#define-the-project-operations-deployment-scenario-for-a-legal-entity

The main idea here is to allow options to users and not force them to undo the work they already have done.

If there is an alternative or a workaround been created for this design choice, please give a clear roadmap or timeline for when it is going to be applied.