Dynamics 365 Project Operations

By default, it is possible to enter a simple amount (priceperunit) on a project-based quote line (quotedetail) when there are no associated quote line details (msdyn_quotelinetransaction). This is perfectly reasonable.

At the quote level, there is a "Recalculate" button (msdyn.quote.buttons.Recalculate) that recalculates the quote amounts, such as when role prices in the price list change.

However, for quote lines without any quote line details, the recalculation logic currently sets the amount of these lines to "0."

This behavior should be revised, and the correct amount from the quote lines should be used instead.

We have a scenario where Bill to address is different than ship to address. As per conversation with MS Support team, they suggested to use Invoice Account functionality. When we are trying to use Invoice account functionality for project invoices, we found out that it is not working for PMA nor for Purchase Order or Sales Order invoicing if we are assigning the Project in "Project" Tab.

Further adding to this point if Invoice account functionality works as expected when bill to and ship to addresses are different during Sales Invoice & Purchase Invoice (without Project tagged) then same functionality should work for Project Invoices as well. Currently as per MS Support team, all information is flown based on the funding source, which is associated with billing for respective customer, however invoice account functionality in Project invoices will provide feasibility to select another customer address different from funding source customer address to compute GST accordingly and all the related information also flows in requisite reports based on the same data.

Scenario: Since, we are a Service based company and majorly using Project invoices for billing to customers, we have a lot cases where the requirement from the customer is to bill the parent company however delivery address should be of child/subsidiary company wherein Funding customer is parent company and with the help of invoice account functionality we can assign child company address by selecting Child customer account. We cannot keep on adding addresses of child comapny in the Customer master of Parent company, we expect a permanent solution for this.

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.

It would be extremely beneficial if one was able to add custom columns to plans, but smart columns - those that are created in the dataverse project task table, thus enabling proper lookups and pre-defined choices. The lack of this feature is basically making the planner a toy tool, not a real project planner.

Here is an example:

It would be good to be able to attach a related value right off from the planner level.

Also, sometimes we might have to track multiple parameters like Planned Start, Requested Start, Assigned Start, Actual Start and so on, but currently it is impossible with the toy custom columns introduced by the planner.

Description:

The system requires a WBS to be published before attachments can be added to WBS ID lines. This limitation restricts users from attaching important project-related documents during the planning and preparation phase when the WBS is still in draft mode.

Proposed Enhancement:

Introduce the ability to attach documents to WBS ID lines while the WBS is still in draft mode, eliminating the need for publication first.

Benefits of This Enhancement:

• Improved Workflow Efficiency: Users can upload, reference, and review essential documents without needing to finalize and publish the WBS.
• Enhanced Consistency: Aligns with other areas of the system that allow attachments to be added to records in draft stages.
• Better Planning Flexibility: Supports project teams by allowing full utilization of the WBS for early-stage tracking and collaboration.

We are unable to run discount on revenue recognition in fixed price contracts (Straight line method) through projects and simultaneously accounting impact on D365 F&O. Since this functionality is not available in current system as it impacting our Business, request you to prioritize this issue.

We would suggest that the system would be able to process project hour journals in the "Project management and accounting" module in D365 F&O as efficiently as possible. If a journal of +5000 lines would be processed more efficiently if split in 15 journals, and run in batch, we would recommend the system would process the job in that way. Hence, when a user initiates the posting of a journal, the size of the journal should have a minimal impact on performance.

This is for Finance and Operations Dynamics in the Project Management and Accounting module. When creating an invoice proposal there's an option to create a fee. However, you cannot choose the line property of the fee. This can create scenarios where the default line property of the project is nonbillable but the fee should be created as billable to invoice. The system doesn't correct for this and doesn't give you the option to correc the line property during fee journal creation. Instead you're stuck with a nonbillable transaction that gets invoiced out and shows as if it's nonchargeable in posted transactions even though it's fully invoiced. Just adding an option to select the line property when creating the fee journal would fix this issue.

The D365 system allows us for posting negative journals because it only checks for overruns, not underruns. This means the system permits transactions that go below the budget and journal entries give users full control over postings, allowing negative amounts to be posted, which can lead to budget underruns.

While the system can handle budget overruns by disallowing or warning users, there is no similar control for budget underruns.

My example below will show what we are thinking.

1. I have an investment project budget with approved budget of 1000
2. Then I posted a PO of 1000 using cost category map to capex project category. (GL gets hit and CIP gets hit)
3. Now someone goes in and post an expense journal using the same capex project category with -1000. ( the CIP is cleared)
4. However, on a budget nothing changes. (no effect with the negative posting)
5. Now, if the user tries to post further negative expense journal they still can. Further affecting the ledger with negative posting.

The design might not have impact on subledger but the ledger balance will not match with sub ledger because of this. 

In a real life situation it is like

1. I have 5 in my pocket
2. I bought something for 5
3. Now the budget is 0
4. Then I go and return 10
5. The system is allowing.

Logically, you should only be allowed to return 5. And the return value of 5 should correct the budget. 10 should never be allowed to post. Furthermore, if the 5 is already estimated to FA, then it should not be allowed to be reduced by any means.

In Dynamics365 F&O in module Project Management and Accounting:

When using the budget control on projects in Dynamics we are not able to all committed / actual costs in the project budget balance report.

The project budget balance report only show balances (committed costs / Actual costs) on categories that have been budgeted on.

However, If we choose the possibility to allow overrun in our budget control parameters, then we might run in to, that we will have costs recorded on categories, that has not been budgeted.

And therefore the report should indeed show all committed / actual costs on all categories and not only on categories that has been budgeted on.