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.

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.