Dynamics 365 Project Operations

In the Hourly, Daily, Weekly, and Monthly Schedule Boards - we need to see in a single line on the schedule board that allows us to use a short name rather than the full client name - some client names are too long and make the schedule board look cluttered.

Maybe adding a short name in the booking pop up that will put the short name field on the schedule.

Maybe some sort of automation that looks at the client name and auto generates using the first 5 digits of first word, the first 5 digits of the second word etc.

Currently, you can only set a 'Number sequence' for Purchase orders from the Procurement and sourcing module.

There is no option to set a 'Number sequence' for Purchase orders that are specifically created from Projects. Thus, for example, there is no way to set a prefix on Project Purchase order numbers that is different to non-Project POs.

Please consider adding that option as some businesses require different numbering on POs if they are raised from Projects.

Thank you!

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!

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 the end user (time sheet creator) has no simple ability to adjust submitted/posted time entries, apart from creating an additional timesheet with a DR/CR entry on time.

Not all end users will have access to Project Management: Adjust Transactions (due to role security).

We are seeking a simple interface (which supports intercompany) where an end user can adjust submitted time (on mass) - The interface should create the incremental adjustment crediting the original entry and allocating the time to the new project. All corrections should be subject to workflow approval (as per original timesheet).

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.

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.

It is a common requirement for a client to be able to customise the number sequence associated to a record. This allows a business to; easily identify records, enable business centric reporting & ensure the volume of records with a unique identifier can be generated in line with the businesses needs.

This functionality is available across Project Operations, see examples such as: msdyn_partynumber & msdyn_projectnumber

However, the same customisations cannot be applied to the Subcontract & Subcontract line records.

The suggestion is enable users to add the fields: Subcontract Number (msdyn_subcontractnumber) & Subcontract Line ID (msdyn_subcontractlinenumber) - to solutions & enable customisation to allow users to define their own number sequences on the Subcontract & Subcontract Line level.

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.