Dynamics 365 Project Operations

It should be possible but we are unable to create a custom price list when the price list contains a Bundle product.

User's are unable to apply discounts or custom rates due to this missing feature

Currently, the CDX.DEMO tenant does not support Project Operations (PO), and there is no dedicated demo available for it. While customers can use the CDX Demo Experience to explore Sales and Customer Service, and PSA is available (albeit with compatibility limitations due to old licenses), the absence of Project Operations licenses means PO cannot be deployed.

To explore Project Operations, customers must provision a trial environment, which requires the use of a credit card. Additionally, since the CDX tenant is a demo environment, purchasing licenses is not an option.

Including Project Operations in the CDX Tenant Demo would significantly benefit customers, allowing them to explore and evaluate PO without the need to set up a trial or provide credit card details. This enhancement would streamline the demo process and provide a more comprehensive experience within the CDX Demo platform.

Benefits:

• Simplifies the evaluation process for customers.
• Eliminates the need for provisioning trials using credit cards.
• Offers a unified demo experience across multiple Dynamics 365 modules, including Project Operations.

This inclusion would address a common pain point and improve the overall utility of the CDX.DEMO environment for customers.

Intercompany hours (hours by IC resources) can be posted by timesheet only. However, it is not possible to address IC resources in the Hour journal. If the pre-selected filter by "Resouce legal entity" is taken away, no IC resources show up. We would like to have the possibility to post IC project hours by Hour journal as well.

Currently in OOB there's no check in system regarding assignment or booking end date on project for a resource when creating time entry. Users can fill the time entry even after the end date of assignment or booking.

System should check the end date of assignment or booking for the resource on project and should not allow to submit time entry after the end date.

If we are making the project as deactivated and still allowing the user to go ahead and do the resource booking process, we are blocking the resource against an inactive project and make them unavailable for any new resource requirements.

In the Project Management module of D365, there is an option to add budgets to projects. However, it's mandatory to use an approval workflow when working with these budgets. Unlike other workflows in D365, the project budget workflow does not allow for automated approvals or the option to bypass the approval process entirely.

This is inconsistent with other workflows in the system, which can be disabled by deactivating the version.

The goal of this idea is to enable the use of project budgets without requiring a workflow for approval.

Thanks!

Within the context of project and subproject hierarchies, budget control offers the option to utilize alternative project budgets. This feature is particularly advantageous for establishing a budget at the parent project level while linking multiple subprojects to the same budget. However, a significant issue arises when transactions are adjusted from the parent project to the subproject; these transactions are counted twice in the budget, which is incorrect as they are not new transactions. To ensure accurate budget reporting, adjusted transactions should be excluded from the budget consumed amounts.

In the Projects module of D365, it is possible to transfer transactions between projects, which offers significant flexibility. However, there is a notable concern: these adjusted transactions are recorded as new transactions in the target projects for revenue recognition purposes. This presents an issue, particularly for capital projects, as it leads to the duplication of postings in the "Construction in Progress" (CIP) accounts. Specifically, postings to these accounts are made initially when they are first recorded and the project is estimated, and then again when adjustments are made to a new project. As a result, this process can result in inaccurate balances in the CIP accounts.

It would be beneficial if adjusted transactions were excluded from revenue recognition processes, particularly in the context of capital project estimations.

Dynamics 365 Finance provides a feature called 'Accounting Source Explorer' which allows a finance user to look at a set of voucher transactions in the GL and have information from the source document displayed in a single view. This is useful for reconciliation and can be exported to Excel to pivot and identify transactions which are contributing to a balance. In standard, information from source documents is provided for customer and supplier invoices and expense reports only.

It could be incredibly useful to include the transactions that are posted from the Project Operations Integration Journal as a source document. It should apply to all transaction types (Hours/Expense/Fee/Materials) and fields could be included such as Project ID, Task ID, Worker ID, Resource name, Transaction category name, Chargeability, Quantity, Transaction date.

The default (not re-imagined) workspace does not allow users to Open Other User's Expenses (which exists as an action button in in other expense module forms).

The suggestion here is to implement a selector (much like exists in the re-imagined workspace) that would filter for other user's expenses and allow the user to view and take action on them.