Dynamics 365 Project Operations

Applying a calendar template to resources can currently be done using one button in the "Calendar Settings." 

However, the application of the calendar template is limited to a maximum of 25 resources.

If there are hundreds of resources, you need to repeatedly execute the calendar settings button, which is cumbersome and inefficient for business operations. Additionally, for users with more than 1,000 resources, repeatedly executing the calendar settings button requires an enormous amount of time, causing significant disruption to their work.

Therefore, having only one calendar settings button to apply the calendar template to resources is very inconvenient and user-unfriendly.

As a standard feature, we believe that setting the limit in units of hundreds or allowing customers to remove the limit through their operations, as well as building functions or applications specialized in resource management (including calendar settings), would improve convenience and enhance business efficiency by making it easier to manage a large number of resources.

So, I hope they improve the functionality of applying calendar templates to resources.

Currently, there is no function to delete achievements, and there are no realistic plans to implement this function.

There is a restriction on achievements that prevents achievement data from being deleted from the system, and this is set to protect the integration with financial and accounting functions in project management.

As a result, this restriction cannot be lifted, and achievements cannot be deleted.

In addition, the project itself in which achievements exist cannot be deleted, and due to a design issue, there is no workaround.

However, a lot of data is stored during the course of work, and capacity is consumed every day.

For this reason, being able to delete unnecessary projects with registered achievements and achievements that are no longer necessary can free up some data capacity, and the ability to delete achievements is also convenient in terms of data management.

So, we hope that the function to delete achievements will be implemented.

Create a parent project and a Subproject. Same Project group but different dimensions. 

Register a cost for parent project.

Adjust the transaction, to move cost from Parent Project to Subproject. 

GL records incorrectly, original entry is not reversed.  

Expectation: the original entry should have been reversed, the correct accounting with proper dimensions to be created and post to subproject.

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 ability to customize the “worker type” is not implemented.

The addition of this feature would improve convenience for users.

We would like to be able to register actual man-hours, actual expenses, and actual material usage, and have them reflected in the project results without approval. The current operation requires approval in order to be reflected in the project. This would make Dynamics 365 more convenient.

This is relating to KB975236, issue is unable to open Project invoice journal form for the Project which has more than 2000 invoices.

Currently, the workaround is to apply a filter to limit the results to less than 2000 records.

However, we would like to have the fix in the future releases.

Indirect costs are usually set up in accordance with the cost center structure to consume and absorb costs by cost center (analogue: surcharges in the costing sheet). Postings should post costs by cost center as debit and credit, respectively. However, this core connection to Financial dimension values is not considered in the indirect cost component setup - neither in the project category setup.

2 possibilities: Add the Financial dimensions to either project category master (in this case, additional possibilities to generally consider dimensions in project transactions), or at least to the "Indirect cost component" table.

In this case, generally requested funtionality can be covered.

End users should have the ability to create timesheets (by default) empty or from favourites - We are seeking a new Y/N variable be placed within user preferences to control the form access when creating timesheets. This variable will drive the default setting of the variable "Create from Favourites".

The creation of the variable will allow a user to define and control how their timesheets are created within the system - Giving them greater ownership and management of timesheet entry.

In addition to the above variable on user preferences we also believe their should be a parameter field controlling the ability for an end user to define their own user preference - This will provide an organisation control over the ability for end users to define how a timesheet is created.

These form controls should support both desktop and mobile interfaces for creating timesheets.

Currently, when user select their own local language and submit the expense report, the approval will also view the submitter's language rather than their own language in ID and Document type columns in "Work items assigned to me" form. Ideally, the data in ID and Document type columns should be shown in the approver's language, no matter the language setup of the submitter.