Dynamics 365 Project Operations

Currently there is no way for the Payroll Manager to adjust timesheets prior to submitting the hours to payroll. It is important that they have the ability to do so in order to adjust time for things such as leave without pay. The only method right now is to make payroll part of the workflow which means that they would need to approve each timesheet every week. This leads to a heavy workload. This new idea is to give the overall ability for the payroll manager to adjust approved timesheets for administrative reasons prior to submitted to payroll processes.

sdfdsfdsfdsfs

After a resource requirement has been raised it needs to carry additional information about the tasks and the assignments to which it relates to assist a resource manager to understand the details of the requirement more.

Currently it only has a link to the project and characteristics about the resource.

Credit card limit field on the employee payment method table. This can then be used to create an alert when monthly transactions are approaching this limit. There is an overnight import of corporate credit card transactions that provides up to date data.

This alert would then be used to a start a review process whether to increase the credit limit or to make an additional payment against the credit card.

In MS DAX 2012 there was a view under the project invoice proposal grid that allowed users to view an invoice summary without going into each invoice project proposal. On D365 we are not having this view.

Customer have tried alternatives to the above with enabling the “New invoice summary page available from Project invoice proposals and Project invoices list pages” functionality but again this requires the users to go into each invoice project proposal to see an invoice summary.

The customer has also investigated of customizing the view to include the invoice summary in the footer, but this could lead to performance issues.

Summary

Improve the system's error handling mechanisms and documentation to provide clarity and guidance when users encounter limitations with multiple project parameters in Dynamics 365 Project Operations.

Issue Background

Users previously had the ability to create multiple project parameters within Dynamics 365 Project Operations. This feature was recently removed or limited without proper documentation or guideline for existing configurations where multiple parameters are in use. This led to business process errors, disrupting the ability to save new projects.

Problem Statement

1. Lack of clear documentation or guidance on changes related to the limitation of creating multiple project parameters.
2. Business process errors with no immediate workaround guidance can significantly impact business operations.

Proposed Solution

1. Error Messages: Implement more descriptive error messages that not only specify the issue but also guide the user on how to resolve it. For example, if more than one project parameter exists, the error should state so and guide the user on deactivating the "PreValidateProjectParameterDelete" plugin to resolve the issue.
2. Documentation: Update the Dynamics 365 Project Operations documentation to detail the limitations around project parameters, including potential issues and resolution steps.
3. Change Management: Release guidelines in advance of the change to allow businesses time to adapt their processes. This should be part of a well-structured change management process.

On all project operation objects, quotes, contracts, projects the systems displays a party ID instead of a useful text value. The system requires you to click into each attribute to see what it is. Not an ideal UX. Can it be displayed to the TEXT values not a random ID?

There must be one more tab in Projects as Project Profitability which should give summarized results about proposal vs contract and project actuals lime tracking, estimates, resource assignment and resource reconciliation.

Microsoft issue 828584 - project item journal does not post the expected inter-unit transactions when using balancing financial dimension and inventory dimension link.

Microsoft acknowledges this missing Inter-unit posting but is electing to not correct this due to existing customers using the standard functionality. I would like to suggest that a paramger flag be created "Enable item inter-unit positng" - YES/NO. If NO, then existing functionality will continue and if YES, then the inter-unit entry will be made for the item posting.

The ability to change companies, legal entities so that managers can approve expense reports for workers in different legal entities.

This maybe a limitation of the app connector to the Dataverse. My understanding is that the user default legal entity is used.

Please advise if there is a workaround for this and what long term development is planned.