Comments
My vote for this idea, this could be really useful. For example, a simple task like finding the first/last sales date for an SKU sometimes requires hundreds of thousands of database queries, since we have to query each combination of item/variant/location separately. SELECT MIN([[Posting Date]) with GROUP BY would be much more efficient.
(My links to LCS issue number 978720 - "Coupons buttion is disabled for return order" were rejected as malicious. See the text of their remarks below)REMARKS"We understand the issue where the Coupons button under the Manage tab of sales orders is enabled only when the sales order type is "Sales order" and it is a retail order. This behavior has been in place for years. Currently, we do not plan to make changes to this functionality. However, we will monitor if customers express a strong need for this adjustment in the future.Additionally, the parameter "Manual entry of coupon codes for return without receipt" in Commerce parameters determines whether, for order lines with negative quantities, a coupon code must be manually entered to apply the associated coupon discount. Customers currently can use this functionality in orders with type as sales order, or in POS side. "
Some might consider this a bug, and they'd be right. But the product team acknowledged the bug and chose not to address it because essentially, "it's always been like this".We generally expect Microsoft to be ahead of the times and be a force of change as opportunities to improve present themselves. Today, they are not. Maybe they'll consider fixing their mistakes in the future. To be seen.
We also see a security gap here. The warehouse employees do not all have their own Entra ID, as they are employed as temporary workers, for example. It is not safe that one user set passwords for all MDE workers. There should be a function that specifies that the password is an initial one. The worker should then have to set their own password in the app the first time they use it. It should be possible to define password rules for the companies themselves and it must be possible to assign your own password within the app, as the warehouse employees do not have a regular computer at their disposal.
This is a great post. We have been working around this issue for some time. On some lines, we have to receive the same line up to 10 times if there are markings to the PO line. This is extremely inefficient. We should only receive one PO line which then marks to the corresponding demand lines.