Sreedhar Burgula

Period type is Week with auto-split in case of month end. Week starts on Monday. Saturday and Sunday are not working days as per the calendar attached to the project resources. 

Missing timesheet notification should not be sent if the period includes non-working days. 

Example: There are cases, in which a period contains non-working days only. example: Saturday-Sunday, e.g. April 1- April 2, 2023. 

Since these are non-working days, the users should not receive a missing timesheet email. Currently, it seems that this cannot be avoided. 

If the project has the sub projects, when we create forecast for the Main project and sub projects.

When we open the All-forecast form, there is no option to "Include sub projects" on the form. All the forecasts are displayed on the form.

The INCLUDE SUBPROJECTS logic should be available everywhere, not only in some forms.

The On-account transactions form doesn’t have the credit note transactions, this can be tracked from the Invoice journals.

There is currently no overview of posted credit note transactions. The only way to check if a credit note was sent is via the invoice journals. However, when the number of invoices becomes large enough, finding a credit note becomes challenging. Furthermore, in the on-account transactions form, the original transaction remains without any matching credit note transactions. This can be confusing for the end users.  

Creating a project production order with a consumed posting type should be allowed even though the costing sheet exists.

Below is the scenario

According to IFRS and POC if we have a production order lasting 24 months, and each month we consume raw material, overhead, hours, they have to go into costs so that with POC logic (%complete) 

We can achieve a revenue. If we can’t use posting method consumed, we stay 23 months with 0 costs and 0 revenues and then, when machine is reported as finished and so basically invoiced, I have all my costs and so my revenue.

This is not correct for an accounting perspective.

Customer would like to have the Reason code used for the project accounting and management module.

In General ledger > Journal setup > Financial reasons there are a reason codes that we use when posting GL journal lines. It is suitable to be used only for Ledger, Asset, Bank, Customer and Vendor account types, but in GL we have also a Project account type for which we couldn’t find the reason code setup.

We are facing the problem that we cannot use Reason Code when posting GL with account types of Projects.

Once an expense report is created an expense line is created on default with zero amount

From a technical standpoint, we wanted to verify how we can prevent that line from being created in the first place. I know it’s working by design and that’s ok for most of our needs, but we have specific scenarios where we’d like the user to settle their credit card transactions before creating a regular expense line, and this creates an issue because they’ll be able to enter information there before even getting to add an unattached expense. We tried removing it or halting the creation process through code extensions, but none of that worked for us.



The objective of this Idea is to implement the above business scenario on D365 application.

The issue appears during invoicing process from project based on the created sales order on the project. If sales order lines are used to create invoice proposal, on the invoice proposal form there is no information about the referenced sales order ID. There is also no possibility to add the filed by personalization (Insert columns...) It causes much inconvenience because the person responsible for creating invoice proposal has to look on all sales orders created on the project in a different screen, compare and search for the correct line.

During project lifecycle quite many sales orders could be created and double checking extends the time and make the process not optimal.

The sales order ID field with reference to the sales order where the sales order line has been created should be added to the invoice proposal form. It is applicable for invoicing sales order lines scenario (Transaction origin = Sales order).

The GBR document is “Posted” the Budget control statistics by period> Budget reservations for encumbrances have the status as “Confirmed.”

The GBR document is “Finalized” the Budget control statistics by period> Budget reservations for encumbrances have the status also as “Confirmed.”

The status of the GBR document when "Finalized" shouldn't be the same as when the GBR document is "Posted."

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.

1. Create a Budget plan Hierarchy publish 

2, Adddit to a Budget planning process - create budget plans

3. Modify your organisation hierarchy and re piublish it

4. Your Budget planning process using the above hierarchy is not updated - or it won't allow you to edit as well.

We understand this is working as current design. Customer has to configure the Organization first and then use it in budget planning process.

This functionality is a common practice in the business, we request this to be consider in the next road map.