Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
Why does it take so long to implement a quick win like this?
Any progress on this?
This idea is open for 3 years already.. :) Over time I have learned.
Maybe we would be even better helped, by having connector to Data Lake instead.
I know a data lake export is expected. Import from data lake would make this complete.
The import could just see the lake as blob storage... Shouldn't take 3 years... Right.. :)
Companies that do project manufacturing need to keep track of the physical inventory even though the cost of the purchase is recorded towards the project. As a workaround, instead the project purchase is created from a planned order from master scheduling (coming from the project item forecast for the parent item), there is no way for the receiving/inventory people to know that that particular purchase item is for a particular project. It becomes especially challenging when the company works in FIFO cost method. They need to get the purchase cost and the item batch/lot number for that particular purchase to the specific project. There needs to be a flag to allow for tracking the physical inventory that is purchased for a project.
This is a must have in any refurbishment scenarios as well as asset management where spare parts are reconditioned.
- users can distinguish again between views and records again and
- the number of items in Recent Records will be increased again or this number has to be changed by an admin user.
Report 5500 "Prod. Order Comp. and Routing" is quite good to start with. Though it has a it different layout, but is far more better than the 990000762 report. And this can be changed on the Report Selections.
Though, I do agree, that the 990000762 report is quite awful report, and it does not serve a purpose.
Same for the Purchase module.
Table "Purchase Line", Text018:
Text018: Label '%1 %2 is earlier than the work date %3.';
Possible solutions (or implemet both):
1. Convert into a notification, so that it does not stop the data-entry flow of the user. Let the user disable this notification from the "My Notifications" page.
2. Be able to disable the message from code by raising an event that we can subscribe to.