Dynamics 365 Project Operations

Creating a project production order with a consumed posting type should be allowed even though the costing sheet exists.

Below is the scenario

According to IFRS and POC if we have a production order lasting 24 months, and each month we consume raw material, overhead, hours, they have to go into costs so that with POC logic (%complete) 

We can achieve a revenue. If we can’t use posting method consumed, we stay 23 months with 0 costs and 0 revenues and then, when machine is reported as finished and so basically invoiced, I have all my costs and so my revenue.

This is not correct for an accounting perspective.

The On-account transactions form doesn’t have the credit note transactions, this can be tracked from the Invoice journals.

There is currently no overview of posted credit note transactions. The only way to check if a credit note was sent is via the invoice journals. However, when the number of invoices becomes large enough, finding a credit note becomes challenging. Furthermore, in the on-account transactions form, the original transaction remains without any matching credit note transactions. This can be confusing for the end users.  

Currently, the project contract can only either be in status Draft or Confirmed. Because after the contract is confirmed it can no longer be edited, Microsoft suggests to keep it in status Draft. That is misleading for Account managers and Project managers. Thefore, a new status should exist between Draft and Confirmed to signal that the project contract is complete, such as Ready or Qualified. If a new status is introduced, the Draft status should prevent invoicing.

We need to have a notification sent for proactive quality updates similar to how we get service updates schedule and notification in case production environment is not upgraded to higher versions (lesser than two versions) than the currently released version. The updates sent for proactive quality updates will help us to prepare for scenarios where the deployable packages are built on lower versions for future deployments whereas the Production is meanwhile upgraded with higher application versions (through proactive quality updates) before even the deployable package is actually scheduled for deployment to Production.

This will also help is in minimizing the risk of missing the deployment schedules specially in case the deployment schedule is very limited for implementations across the globe.

The above scenario was recently faced by our team which lead us to raise this idea.

Regarding Dynamics 365 Project Operations, currently, there is no default feature to automatically relate roles from selected bookable resources when creating project records.

When creating Project records, according to selected bookable resource records on "Project manager" fields on the form, team member is added to the created Project record.

The role of this added team member would be always "Project Manager" instead of related roles from selected bookable resources.

However, some users would like to set related roles when creating project records.

It would be great if related roles with selected bookable resources could be set by default features including Power Automate.

With the current functionality, it is not possible to create new lines in the contract lines tab after an order has been received.

However, if we want to use the same sales order data to manage the excess of the contract after the order is received, the feature to create a new line in the contract lines tab of the sales order data after the order is received will improve convenience.

On "Expense Estimate" tab in a project record form, users must manually a record one by one.

When creating "Expense Estimate" on it, it takes some to process.

Users would like to register multiple "Expense Estimate" records on it, but it takes a huge time.

It would be great for users to have a feature to import or register the records in bulk on "Expense Estimate" tab in a project record form.

While creating the budget the forecast models are usually pre-filled with Original and Remaining. Given this, inspite of drop down showing Remaining , if someone forcefully types Original there is no check to stop it. if the user types an incorrect value project budget will be mixed and provide incorrect values.

It would be great to have a check to stop incorrect values to be captured.

It would be great to have the ability to automatically update the price of a quote when a team member's role changes in Dynamics 365 Project Operation.