Dynamics 365 Project Operations

The project invoice form for the GST group is currently generating inaccurate values for each invoice.

When we attempt to check the GST group in Visual Studio, the data is processed for localization purposes, which causes the incorrect GST group to display, rather than the correct GST group associated with the lines in the invoice.

As a result, we are required to review each invoice individually to confirm the corresponding GST group, which is proving to be an inefficient and time-consuming process.

When editing bookings for which span over several weeks or months. We would like to set a particular period to 0 hours which would cancel out those bookings for that time frame.

Currently the lowest we can set it to is 1 hour which is not ideal.

Example - 'https://imgur.com/a/1B77hsg'

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.

Project management and accounting > Setup > Posting > Default offset accounts for expenses. This table should allow for a GL account specification based on the project group.

The Calendar tab had appeared on the project form. In practice, this "wall calendar" is not used in the project environment. Therefore, the Calendar tab could be hidden by default on the project form.

In September 2024, the Calendar tab appeared in the Project for the Web environment of several customers. The tab was visible in all projects. It couldn't be hidden through configuration. The Calendar tab could only be hidden in new projects.

Currently, under the Job Task section, "Labels" is a column that can be added to the Project Task section in Project Operations. This column allows the user to add customizable (coloured) tags to Job Tasks in the Grid View.

However, in dashboard and views, users are unable to select "Labels" as a field/column. For example, the fields "Bucket" and "Priority" are reportable fields in the dashboard/views, but "Labels" does not exist.

The request is to ADD "Labels" as a field (field from the Job Task section of a Job) to be added as a column in Dashboards and Views.

Customer highlighted that if he has a project created in a legal entity with intercompany relation.

If hours are submitted in a timesheet to the secondary legal entity

it will not reflect in the coast estimates in the project for the main entity unless they are posted manually as pending invoices which is a very tedious process.

Ability to select number sequence per project group. This will allow users to have different project ID numbering. Making it easier to identify the source / purpose of the project. This also has other advancatages, such as:

• improved workflow conditions for other modules; many workflow use the project ID as condition but not the project type / group, a different identifier against the project ID would allow for more advanced workflow conditions

Validation for the project/category relationship should be extended to enable validation at the project type or project group level in addition to the project ID level. This could easily be achieved by providing a Type, Group, or Table option similar to the Project Ledger posting setup. In many cases, users want to restrict available categories based on the project type or group; this feature would give users that flexibility with little-to-no maintenance unlike the Project specific validation they have today.

Currently when an invoice proposal is posted and the invoice journal has automatically been created the lines on the invoice journal are ordered alphabetically by the project category and not in line number sequences like the sales order and invoice proposal.

This then means that the output document to the customer is in a different order to the documents they have already received.

We would like to see consistency with the sales order and invoice proposal by having the sequence be by line number and this would also be in line with the Sales invoice