on
RE:
Needed - Now we are using the field "Reason for Export"
RE:
Could be very useful as this will let the purchasers know that there is not a purchase price and they might need to insert the purchase price themself after confirmation from the vendor
RE:
It would be good to have a fix - uploading statements in bulk makes it harder to automate when you need to go and enter the opening balance on a daily basis
RE:
Hello,I hope this helps. I believe this functionality is already available in Dynamics 365 Contact Center. However, it is configured at the queue level, not at the workstream level. In the queue configuration, you can set overflow rules to redirect calls to, for example, another queue.Is this what you are trying to do?
RE:
I would also suggest to show the agent in the pop up with the callback request from which queue the callback is coming.
RE:
This is indeed a critical feature, as it will solve problems for many customers and significantly enhance their supply chain management (SCM) processes.
RE:
Yes please! I'd love to be able to provide reporting based on the ship to!!
RE:
A good idea would be for Microsoft to communicate this information in the Message Center through the Release Notes of the Microsoft Dataverse version.https://learn.microsoft.com/fr-fr/dynamics365/released-versions/microsoft-dataverse
RE:
In addition to adding this functionality directly on the Purchase order it would also be useful to have it on quotations and sales orders.
RE:
Issue is still open and will hopefully be fixed in 10.0.45See comment below from Microsoft Support:From the details you've provided, it seems that you're encountering persistent warning messages during Planning Optimization (PLOP) execution. Specifically, these warnings indicate that certain unit of measure IDs are missing. Upon initial research, I've found that other customers had already logged bugs to address this behaviour. Initially, this issue was supposed to be addressed in release 10.0.42. However, it has since been converted into a deliverable. Deliverables are opportunities for improvement, but they are not treated as bugs. This particular issue has been recognised and will be considered in future updates. Since it is not classified as a malfunction, it is not a top priority, and there is no defined timeline for resolution. I have communicated your requirements to the Product Group and encouraged them to prioritise this issue. Although the estimated completion of the deliverable is currently for release 10.0.45, this is not definitive and may be subject to change. My suggestion is to wait for version 10.0.45. If the issue persists, I encourage you to submit a new SR referencing Deliverable 964201 to get an update on the status.