on
RE:
The restricted regions feature is required for compliance within our distribution workflow. This is essential to ensure the correct product is shipped to the correct region and countries do not receive products that are not regulated for use in that country.
RE:
We've come across the same issue that's quite serious in our pharmaceutical implementation of D365. The restricted regions feature is essential for compliance, especially when it comes to making sure products aren’t shipped to countries or areas where they’re not authorised.At the moment, this control seems to work fine when raising a standard sales order – but not when the order is created via a project. From a business and compliance perspective, this is a major concern. There’s really no reason the system should behave differently depending on how the sales order is raised. In regulated industries like pharma, this kind of inconsistency could lead to product being sent to restricted territories, which has significant legal and safety implications.We’d really appreciate it if this could be looked at with urgency. It’s a critical control and needs to be applied consistently across all sales processes.
RE:
A Project Sales Order and a normal Sales Order to all intents and purposes for the sales teams are exactly the same, apart from the obvious point that a Project SO is for a project. Basic functionality, which has been around for years, such as Restricted Products should be available to a Project SO. I was surprised to learn that a Project SO doesn't allow this functionality.
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.