on
RE:
Have done it for our ISV und would be really important.
RE:
Hi Laurens,Just a quick note on something we’re running into a lot — and I know other companies are struggling with this too.Right now, when we receive an ASN that includes a parent license plate with child license plates, it becomes a real pain if we want to transfer that structure to another warehouse using a transfer order. The only scenario where the parent LP and its child LPs can be transferred together correctly is through the Warehouse transfer menu on the mobile device.But the moment we try doing this with a transfer order, things break down. Either the system throws an error after packing into a nested license plate, or it forces us to create a new license plate — which basically undoes the packing structure we just set up. That’s not ideal, and it's slowing us down.The bigger issue is that we’re stuck scanning every child license plate individually. That’s a lot of scanning, and it's easy to make mistakes. It would make a big difference if we could just scan the parent license plate and let the system carry the child LPs along with it — like it already does with the warehouse transfer flow.Would be great if the same logic could apply to transfer order picking. Any chance that’s on the roadmap or if there’s a workaround we’re missing?Paul Demarbaix Driven By Passion BV
RE:
is there any update on this?
RE:
Great idea and is often a requirement when using ATP
RE:
Having the ability to Record Dimension Values in the "Map Text to Account" table has been requested by several of our customers and would be a great benefit
RE:
Great idea and a mandatory step to stay with Microsoft D365 compliant within the Pharma industry !
RE:
Great idea and mandatory to stay compliant in pharma industry.
RE:
I feel its very useful
RE:
Considering Microsoft recommends to end users to close down device authentication "search: Block authentication flows with Conditional Access policy." We really need another method for development (Development deploy and download symbols). This is another good reason for adding more authentication methods.
RE:
Timo wrote back in 2019: "As part of Norwegian features, user is able to define which company bank account is chosen depending on i.a Currency. Now, when generating payment proposal, this setup is considered which offset account is used on the payment journal line. But user is not able to generate one file to sent to the bank but must generate payment file per bank account."Why is this function only made for Norway? We are currenctly implementing companies in different countries in the same environment and have to find different processes due to the tables BankCustPaymModeBankAccounts and BankVendPaymModeBankAccounts not being available for all countries.