Dynamics 365 Project Operations

We need the ability to add expenses directly when creating an Expense Report in the Expense Management PowerAPP. Currently, the functionality only supports creating an expense first and then selecting it to create the expense report. This behavior differs from the D365FO UI and the old mobile app.

In D365 F&O, when a project is selected in an Item Journal line, the financial dimensions are inherited from the project master record and applied to both the debit and credit sides of the voucher posting. By default, the system debits the project for the cost and credits the transaction based on the item’s inventory posting which is balance sheet. Most of the times, customers use different account structures for Balance Sheet and P&L accounts and item journal can fail to post. By providing a separate offset account string for items, this error can be avoided, and client can use different financial dimension combinations for "Inventory-issue" type side of voucher posting ONLY. 

Example:

Preconcepts:

• Site is configured with a Financial Dimension.
• The Financial Dimensions configured for Sites have also Derived Dimensions values.
• When an order is created (PO or SO) and a Site is selected, all financial dimensions are populated based on the derived dimensions.
• Projects are configured with financial dimensions as well (different than Site financial dimensions).

When an item consumed against a project using an item journal, the credit side of the voucher posting to derive financial dimensions based on the Item’s Site. Customer has linked the Site inventory dimension with a particular financial dimension and configured Derived Dimension values accordingly. Expectation is for the system to inherit financial dimension combinations from the Site inventory dimension for the credit side of the transaction ONLY because the credit line is an inventory-issue type posting. The same behavior is expected if the item journal line has a negative quantity (inventory capitalization) but in this case the financial dimensions will be used on the Debit side of the transaction ONLY.

Note: This new posting logic could be parameterized, for the clients that want to use the current posting logic, this parameter must remain as "No", but for the clients who sees this a good opportunity they can use this parameter to follow new logic.

Clients often times have a pool of resources who can complete a task. There needs to be a way to allow a group or team to be assigned to a task. D365 Field Service has the concept of Bookable Resource Type = Pool. Can this be made availabe in D365 Project Operations?

On large enterprise projects, many tasks can require supporting documentation to demonstrate completion of the task. Integration with SharePoint for document management should match the WBS hierarchy, to allow for a good user experience. For example, task 1.1 should have a corresponding folder 1.1, 1.2 should have a corresponding folder etc. Addtionally, task ownership and Dataverse security should also map to SharePoint, to a provide a clean and scalable user experience.

Currently, we cannot add Financial Dimensions on expense edit form in PowerApps.

Financial Dimensions like Cost center are important for all expenses and financial data analysis.

Field "Exchange rate":

We can add this field on expense edit form in PowerApps.

However, when user changed the exchange rate value rather than system default rate during input expense,

the value user input will never be saved.

Every time user closed and re-opened the same expense again,

it always shows default rate there,

no matter how many times he/she changed the rate.

Please try to fix this "Exchange rate" bug in the PowerApps

and offer financial dimension fields for expense report.

When the revenue recognition ends on 30.11 and you also have posting date 30.11, the exchange rate should not use the actual positing date (2^nd December).

In this example (which are using actual currencies from the actual period), this contract has a difference in contract value on 40735 USD because the exchange rate is using 2^nd December instead of 30^th november. This is making wrong accruals and many contracts with high amounts make very high differences in accruals than would be in the fiscal period end.

Business impact:

The issue of incorrect contract value calculations in fixed-price contracts denominated in foreign currency poses significant financial and operational risks. Specifically, when posting revenue recognition, the exchange rate for these contracts is inaccurately applied, as the rate from December 2nd is used instead of November 30th.

This discrepancy resulted in a $40,735 USD variance in the contract value for a single example, leading to incorrect accruals. When scaled across multiple contracts, particularly those with substantial values, the impact becomes materially significant. Such discrepancies distort financial statements, compromise the accuracy of fiscal period-end reporting, and could lead to regulatory non-compliance or audit findings.

Furthermore, the issue introduces inefficiencies as teams may need to perform manual corrections, increasing workload and the risk of errors. Addressing this problem promptly is crucial to ensure the integrity of financial reporting, maintain stakeholder confidence, and reduce operational inefficiencies.

Please refer to the work item 979192.

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.

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!

Per a client's policy, travelers can only be reimbursed for their travel miles that do not include what their normal commute to their home would be.

The customer requests that the users would have the ability to enter mileage from point A to point B, as well as deduct the amount of milage from their “normal” home-to-office commute.

\