Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
In customer voice, we are improving the email template experience by saving the email template as part of the survey collection. As part of this change, we save the email template (from default CDS) to the specified CDS associated with the project. Please contact firstname.lastname@example.org with your survey URL and email template name if you are still unable to find it.
A full 'license plate tracking' solution would be something like the one available in AX/D365F&O (but better, of course, because it's BC!) (reasonable , but dated, primer here https://axscm.wordpress.com/2015/09/19/using-license-plates-in-ax-2012-wms/)
A 'License Plate' therefore represents a unique identifier for some container (e.g. a pallet) which can hold a number quantity of different items/lots/serials, but can also be moved around a warehouse, put-away. and picked as a single entity. (sitting somewhere between a Bin and a Lot in the BC hierarchy!)
At a minimum users need to be able to create licence plates during the receipt (and output, whse journal, etc.) process, put-away, move, and pick license plates (which automatically puts away, moves and picks ALL inventory assigned to that license plate) and must be able to ship and consume license plates (which ships and consumes some or all of the inventory assigned to that license plate)
Additionally, license plates are not physically indivisible, so users should be able to easily move inventory from a license plate onto a new or existing license plate, and be able to move inventory between license plates.
Hard to compress it into a comment! reach out of you want to talk it through.
Good idea, I'd suggest mirroring the 'Block Movement' functionality that we already have on Bins, such that you can block movement [Inbound|Outbound|All] at the Bin, Zone and Location level.
As an aside; there are workarounds available. If you are using bins you could set all of them to 'Block Movement = All'. If you're not using bins, you could remove the inventory posting setup for this location thus giving the users an error when they try and post.
If you update the worker record address there is an option under "More Options" to select other. Select the legal entity address and the click "More Options" again and then click "Assign to Office Location". The system will now use that address for the employee to assign to PRs/POs and since you linked it to an existing legal entity address, it should update if any changes are made to it. Its an extra step when adding a new worker but works nicely once done. Hope that helps you. :)
Something new with this incident. It is very important for our customers.
Maybe it would be better to provide an OOTB embedded PowerBI experience for quality results, statistics etc.
In any event I vote for your idea as reports are always welcome in the quality arena.
I agree seen this requirement come up a few times on customer projects and always have to extend using development to achieve it.
I agree I have 2 clients who need customisations to the route card. Guess the priority has been on largely external facing documents. Inspection History Certificate is another internal document that often needs changing too as often supplied to customers as evidence of testing.
I should had wroten "The only one in the system that allows getting the balance detailed, only showing the pending documents at a previous date is the "Aged Accounts Receivable (120)"