Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
This is something the routine business scenerio, this must be consider in future release.
One more important thing with the same business case is;
One PR with 10 lines, 5 lines has been completed the RFQ (VendorA selection) and "Approved". These lines should be available in "Release Approved Purchase Requestions" to proceed with the Purchase order.
Few of our current customers require this feature and would be very useful to include this as a standard feature.
Very necessary, a chat channel on a public website is especially dedicated to leads
Would indeed be a great addition to the slotting feature! Thumbs up!
It also seems that open sales orders with invoiced lines get counted twice. Invoice and on the orders. This cannot be correct. Will it be fixed soon.
Yes please - Removing the Security Entry Point permissions tool in 365 has made editing and reviewing security set up so much harder. Bring the tool back from 2012.
ER format element "convert to PDF" would allow using Excel and Word templates with "PDF Merger" creating composite PDF output from multiple files.
* PO confirmation merged with company-specific static "Purchase terms and conditions" PDF document.
* Sales invoice merged with company-specific static "Shipping and return terms" PDF page
* PO confirmation merged with MTO product specification attached as PDF to the purchase order
Question from Colby Gallagher (Yammer Sept 21 2020):
"Deleting ended production orders is standard clean up activity, there's even a periodic job for it. The financial impacts of an ended production order can't be changed, you have posted route transactions and inventory transactions for all things that happened. Why do you need to prevent deletion of the production order?"
FH: Posted transactions are only part of the story.
To have a clear traceability of the planned vs. as-built production BOM, routing planned vs. spent hours etc, it is important to keep the production order in the system.
I never had a customer who wanted to clean up their production orders.
Even if the Ended production order should be deleted, this clean-up is not part of the normal daily process.
There is a risk that a user who has the permission to delete production orders in status Created, erroneously deletes an Ended production order.
If we consider the similar case for Sales orders, it is possible to get a warning or a block when you touch or try delete an Invoiced sales order. (AR parameters > Updates > Safety level of invoiced orders),
A similar parameter for production orders would mitigate this risk.
Could not post the entire comment the first time so continuing here:
Example of text entered in a single line text field "Name" on Account Entity:
This will be stored successfully. When a user requests data of this record they are able to see the field with data as is and no sanitization/ cleanup.