Dynamics 365 Project Operations

Project quotation journal should have option to track changes made after sending to customer and their revisions after customer asks for changes and resending new quotation. This function is available in Purchase order confirmation journals. This is very important to get to know customer demands

Hi,

In the following 2 scenarios, where we create Production Order from Item requirement, while having PMA parameters: Committed costs OFF for Item requirements, ON for Production orders

S1 - Project Item requirement - Net requirements (Master planning) - Production order

S2 - Project Item requirement - Create Production order

the Committed cost is not being tracked.

It is only tracked when Committed costs for Item requirements are also ON - but the desired behavior is that Committed cost is tracked as well ONLY when it is ON for Production Orders.

Thank you!

How do I expand Projects hierarchy all at once instead of one at a time

The financial records involved in Project Operations (e.g. actuals and transaction origins) get massive in Dataverse database size. Long-Term Retention can archive these records on the Dataverse itself, but the corresponding archive functionality on the ERP side does not have a "functional scenario" to handle project operations data. This causes data to be out of sync and broken if only the Dataverse data is archived.

Currently these are the only existing functional scenarios supported, per the archive documentation:

• Dynamics 365 Finance General ledger
• Dynamics 365 Finance Tax transactions
• Dynamics 365 Supply Chain Management Inventory transactions
• Dynamics 365 Supply Chain Management Inventory journals
• Dynamics 365 Supply Chain Management Sales orders

The suggestion is to add Project Operations records and/or financials as an additional supported functional scenario.

We would like to propose an enhancement to the Project Plan task grid in Dynamics 365 to ensure that changes from generic resources to specific named resources are accurately reflected. Specifically, we suggest the following feature:

Reflect Resource Changes: When a generic resource is created and later changed to a specific named resource in the resource assignment, this change should be reflected in the task tab or project plan tab of the Project Plan task grid.

Current Design Issue:

As per the current design, when a generic resource is created, it shows as a generic resource in the resource assignment. However, when the same generic resource assignment is changed to a named resource over resource assignment, these changes do not reflect in the task tab or the project plan tab's assigned column. This inconsistency can lead to confusion and mismanagement of resources.

Business Requirements:

1. Accurate Resource Tracking: Ensuring that changes from generic to named resources are reflected in the task tab and project plan tab will provide accurate tracking of resource assignments.
2. Improved Resource Management: Reflecting these changes will help project managers and team members to have a clear and updated view of resource assignments, leading to better resource management and allocation.
3. Enhanced Usability: This feature will make the Project Plan task grid more intuitive and user-friendly, reducing the need for manual updates and checks.

Implementing this feature would significantly enhance the user experience in Dynamics 365 by ensuring that resource changes are accurately reflected in the Project Plan task grid. This improvement would lead to better resource management, accurate tracking, and overall satisfaction with the platform.

We would like to propose enhancements to the Project Plan task grid in Dynamics 365 Project Operations to allow for greater customization. Specifically, following features:

Hide Columns: Provide the ability to hide specific columns in the Project Plan task grid. This would help users focus on the most relevant data and reduce clutter.

1. Change Default Column Order: Allow users to change the default order of columns in the Project Plan task grid. This would enable users to prioritize the information that is most important to them, improving efficiency and usability.
2. Remove Unused Columns/Tabs: Offer an option to permanently remove unused columns/tabs from the Project Plan task grid. This would streamline the interface and make it more user-friendly.
3. Change Column Labels: Enable users to change the labels of columns in the Project Plan task grid. This would allow for better alignment with specific business terminology and processes.
4. Customize/Configure Sequence of Columns: Allow users to customize and configure the sequence of columns in the Project Plan task grid. This would provide flexibility to arrange the grid in a way that best suits their business needs.

Business Requirements:

Improved Usability: Customizing the Project Plan task grid to hide, reorder, remove, and relabel columns would make the interface more intuitive and tailored to individual business needs.

Enhanced Focus: By hiding irrelevant columns and relabeling them to match business terminology, users can concentrate on the most critical data, leading to better decision-making and productivity.

Streamlined Interface: Removing unused columns and customizing the sequence would declutter the grid, making it easier to navigate and use.

Implementing these customization options would significantly enhance the user experience in Dynamics 365 Project Operations, making the Project Plan task grid more flexible and aligned with diverse business requirements. I believe these changes would be highly beneficial for users and improve overall satisfaction with the Dynamics 365 Project Operations module.

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.

The financial dimension values from expense report does not transfer to project invoice proposal when the financial dimension of expense account structure is different than project dimension setup. The project invoice proposal inherits the financial dimensions on the main account of the expense, which is set up in Account structure, instead of the dimensions in the Project setup. Therefore, some financial dimensions will become blank on project proposal and unable to post invoice proposal.

However, when comparing with the invoice journal side, the project invoice proposal is picking up all Project default dimensions even though its account structure lacks some dimensions.

This causes an inconsistency in the system behavior and has a serious impact to customers who are using this function to post project invoice proposal for expense report.

When a user needs to enter a mileage expense, they would choose the mileage expense category and key in the number of miles to be expensed. The current system functionality doesn't calculate the total at the bottom of the screen until the user clicks the refresh icon.

If users do not select the refresh icon to calculate the total, they will receive an error that keeps them from entering the expense. This is due to the mobile application having no initial knowledge of the tiers (confirmed by the product team engineer). Unfortunately, this has led to some confusion for users as they expect the total to automatically calculate for them.

I am suggesting that the mobile app automatically calculates the total for mileage expenses, rather than relying on the refresh button to be selected.

The current state is as follows:

1. An intercompany expense (The Header ‘Legal Entity’ is not equal to the ‘Legal Entity For Expenses’)
2. The header ‘Project ID’ requires an activity.
3. Attempts to create the expense from a receipt results in the error: “The activity number is missing. The project that is associated with the expense requires you to enter an activity”

Conversely, the issue is not seen under following scenario:

1. Non-intercompany expense (The Header ‘Legal Entity’ equals the ‘Legal Entity For Expenses’)
2. The header ‘Project ID’ requires an activity.
3. The expense is created with no Project ID and without error (Project ID must be manually set in each expense line).

Recommendation:

1. At minimum, Intercompany expense behavior should be the same as non-intercompany expenses. 
2. Ideally, the ‘Legal entity for expenses’ and ‘Project ID’ fields on header would default on the expense lines without validating the Activity.