Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
This is a must have for any process manufacturer as they typically pick more materials than the formula calls for and is frustrating to have to tell them they have to use round-up or other functionality that doesn't fully meet their needs.
100 % agree.
After base-app and system-app had been made, I think it would make very good sense to create a permission that only grants the user the basic permission in order to log in.
I've just had a case with Microsoft with a tenant here, where a custom permissionset for team-member licensed users lacked one specific 20000x table which caused tenant to be extra loaded and led to instability for the entire tenant.
This would have been avoided, if Microsoft made a basic system-permission set that all users got when created. A base permission to to be able to login. All other permissions set would add additional areas.
For further input, please speak to Dan.email@example.com
This idea has been under review for over a year now.
What is the status?
I would vote for this a million times over if I could. The Inventory Items Navigation list includes Class ID, which is wonderful! Would be so great if vendors and customers offered the same. And having batch ID for transactions - especially sales order processing, so we could transfer to invoice by batch - would be incredible!
This would be especially helpful for companies using Manufacturing, as the right click options are replaced with Job Costing when Manufacturing is used and unless the user goes into PO line detail, it is not possible to delete a line.
This occurs with FIFO periodic.
We have found this incredibly frustrating with clients. It is hard to explain how there is an option to "allow over pick" without supporting the functionality in the mobile device. I second that this is a must have!
Correction on the above. I meant perpetual valuation method, not periodic.
Correction on the above, I meant perpetual valuation methods, not periodic