Dynamics 365 Project Operations

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.

I n project management and accounting module

User is trying to reduce quantity or delete the line on item requirement. This is cause common scenario when the during project lifecycle the requirements are changing. Quantity on the item requirement list is used also for analysis of required and used items.

 Getting error message in Intercompany process The intercompany sales order is being updated, and therefore you cannot add/change/delete lines.

Once a partial quantity is picked we will not be able to change the line quantity

I would like to request a new feature in invoice sending that allows for specifying the last weekday within a given period, instead of just the end of the month.

Currently, there is no way to specify a weekday that falls on the last day of the month within the specified time period, nor can you specify the period as just a weekday.

Adding this feature would provide more flexibility for invoice scheduling.

Project Management - Workspace tile showing records of different legal entity.

Description - In project management workspace the tile count is not updating properly. The tile is showing the records of different legal entity.

Customer Expectation - In DEMF legal entity the tile is showing the USMF entity records., instead it should show DEMF entity records.

Before deprecating the One voucher functionality, one additional scenario needs to be considered:

Account for different Projects on different Purchase order lines within the same PO.

Purchase orders are often split to multiple Projects, where separate Project Ids are selected in different PO lines (within the same PO). These PO lines will add cost to each Project, and need to be included in the same PO.

The One Voucher functionality (when the LedgerParameters.AllowMultipleTransactionsWithinOneVoucher is disabled) will prevent posting the Product receipt and Invoice for the Purchase order.

This is also a valid scenario for Fixed assets to create different Fixed assets per PO line.

Make it possible to correct or cancel packing slips for project item requirements sales orders. At least if the transaction is posted to non time and material project as there is no connection for the transaction to customer invoicing.

All Project entries are recorded on Historical Cost, as determined by the Project Date or the Open Ledger Accounting date (depending on the Parameters set).

When adjusting Project Entries or using the functionality Post Costs. Dual Currency scenario's are not accurately handled and posted.

An enhancement to the process, will be to ensure that Adjustments/Post Costs are performed from the original transaction and that the Accounting Currency and Reporting Currency values are determined off the original posted vouchers or Transaction ID's and not by applying the adjustment date Exchange Rates.

At the moment, date based inputs on Project Accounting creates permanent differences on Reporting Currency and requires consistent Reporting Currency Adjustment journals on Main Accounts prohibited for Manual Posting.

Example:

Source Transaction = ZAR 450.00; Posted: 3 Feb 2022.

Accounting Currency = ZAR, Reporting Currency = USD.

When performing a Post Costs entry and selecting 3 Feb on the transaction - Accounting Currency and Reporting Currency is correctly interpreted.

The Post Costs function is however generally used as an Adjustment event in future periods.

When performing the entry on 7 Feb, the Accounting Currency entry will be correct, but the Reporting Currency scenario will have interpreted the entry on the 7th of Feb and creates a permanent difference on a Balance Sheet account.

Therefore the request to ensure that Project Accounting transactions and adjustments are carried on Historical Cost.