Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
Agree needed and should be on the SKU
Allow a BOM & Route to be set on the SKU & amend prod. order refresh from planning w/s, prod. order line & sales planning would be pretty straight forward to do and follows the principals of a SKU allowing different planning logic per variant / location.
Have had to develop this for multiple implementations. Would be a great standard feature. Voted.
This is very much needed
In BC you can use the Payment Reconciliation Journal to post and apply (match) payments to open customer and vendor ledger entries. You can import bank transactions from file into the journal. The journal also has an auto-matching feature (Apply Automatically) that will assist in the matching process.
Read more here: https://docs.microsoft.com/en-US/dynamics365/business-central/receivables-apply-payments-auto-reconcile-bank-accounts
The idea has been taken care of. Thanks, MS team for the development and solution.
We have finance people who work with multiple entities and it would be extremely helpful if there was an obvious color difference in the form. This would prevent incorrect posting of journals for example (Since we use the same account numbers across entities, this is a real problem)
Version 1.200.34244.4 is changing the verbiage in the menu navigation step.
"Go to Procurement and sourcing > Purchase requisitions > All purchase requisitions."
"Navigate to: PurchReqTableListPage (purchreqtableall)".
We use these tests for manual QA, so I have to go back and resubmit them through LCS to fix them.