-
Voucher for Estimate is posted in accounting currency instead of in project currency.
Customer want to post Estimate for fixed-price project and with Matching principle Production + profit selected in Project group but the currency and amount in voucher is posted in accounting currency instead of in project currency. The feature ‘Enable project contract currency for estimate calculation’ was modified to reflect the correct usage of it: The feature is for the estimation form only and doesn’t impact the change the currency view on the voucher. Customer would like to have option to view and system to post the voucher for Estimate in project currency. -
Changing the dates of a task should not automatically change the dates of other tasks (successor tasks)
In AX2012 this was working correctly meaning it was possible to change the dates of a task without having automatically changed the dates of the other (successor) tasks. The scheduling error was shown, stating the discrepancies or time lags in the dates, but it was possible to decide whether to fix them or not. This is in line with the usually business process as you need to first check the availability of the resources for the other task, prior moving the dates. D365 automatically moves all dates which can cause resource overbookings or misalignment with the actual project progress. Feedback from engineering team is that the design of Dynamics 365 work in the following way: Setting predecessor and successor will have the successor to start date as predecessor finish date + 1. If you have predecessor and successor in D365 the dates will always be +1 and the gap cannot be much bigger. However, user would like to have the option as in AX2012: to be possible to change the dates of a task without having automatically changed the dates of the other (successor) tasks. -
Multiple Timesheet approval
When you need to approve multiple timesheet lines within an employee’s timesheet you need to select the each line and approve that individually. If you select multiple lines the approve button is no longer available.
The current design of the system is not providing this option and some users would like to have the ability to Approve multiple lines/Timesheets.
-
Not possible to see the percentage complete on a total level for the whole project
In an earlier version of FO D365 user had the possibility to see the percentage complete on a total level for the whole project. The feature is now gone.
The estimate calculation now requires that the "forecast" is entered for all transaction types and compares only expense against expense forecast and hour against hour forecast, etc. This is so far correct if we want to look at the forecast for each transaction type. However, the total forecast model should be able to estimate at an overall level.
-
Unable to initiate procurements which spans more than one Financial year because of budget constraints
Customer wants to have one Purchase Requisition in the span of 4 years (2022, 2023, 2024,2025) because the products takes time to be acquired, and they want to start the process early as possible.
Current design does not allow this and engineering team provided a statement: "We do not currently support purchase requisition rollover so any open requisitions need to be cancelled at year end and new ones created in the new fiscal year or they must be moved to a purchase order in the old (same fiscal year) and then rolled over into the new fiscal year. "
-
Project Item Material Reallocation
User would like to have a method of passing reallocation journal for project materials because the current method for adjustments is treating the adjustment as a return to stores and re-issue.
They need a workable solution that does not change the price of the items that were already issued as these would be historical transaction.
-
Batch processing of project work breakdown structure
Business impact: When having numerous projects within Draft status work breakdown structure it takes a lot of time to publish them one by one.
Present system design: The available specified class ProjWorkBreakdownStructurePublishController is not fully designed for use in the Batch Job system.
Request: Publishing multiple project work breakdown structures with Batch job and fully design the available class ProjWorkBreakdownStructurePublishController in the batch job form.
-
"Invoice" is appearing instead of customer name in project tax invoices
Issue: User noticed in the “project invoices” screen, that the Name column is being populated with “Invoice” in some instances. It seems that, when the Name is blank, the invoice is generated correctly but, if a value exists in that Name field, it is being used instead of the client name.
Current design: It was concluded that this is the expected behavior of the system. The Delivery name comes to the invoice name because of the Address of the Customer.
Request: System to take the customer name instead of delivery name.
-
Disable deleting button for WBS tasks which have posted transactions
Currently in the system it is possible to delete WBS tasks, which have related posted transactions. If we do so, the system does not allow us to publish the WBS and throws an error: You have deleted tasks from the WBS that have actuals reported against them. Publishing has failed and the WBS is still in draft and view differences has been enabled.
Workaround is not useful as user looses all modifications made in WBS: If any user deletes one or more WBS lines, which have related posted transactions, the only solution is to restore the WBS to the last published version, but doing so entails the loss of all the modifications the user has done to the WBS. So, it is not a proper workaround.
Product team confirmed this is the design of the system, because if you delete an activity which has posted transactions against it, you break database referential integrity. Publish is already blocking the deletion.
However, user would prefer the Delete button to be blocked in those type of cases to avoid difficult situations.
You’re offline. This is a read only version of the page.
