on
RE:
Table stakes feature. Huge miss that this basic functionality isn't existing.
RE:
You could use the Business Central API for a supported way to extract data. When you connect with dataflow it is actually the API behind the scenes. You could do the same data extraction but better using python in Fabric or else where.regards Jonas Hertzjonas.hertz@bispecialist.se
RE:
This is extremely important for customers would like to utilize this great Physical Inventory Orders feature but they are using Expiration Dates. At the moment, Physical Inventory Orders are totally unusable for these customers...
RE:
I think this is not related to CI-D but to general Dataverse as no edits nor bulk edits are done in CI-D.
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