on
RE:
As a support consultant, I can confirm that the current system is inflexible and can cause significant headaches to the customer and their partner support alike.The proposed changes, if implemented, will make life much easier for both sides.
RE:
Procurement category is a dimension in the model. It currently conforms to these facts: Product receiptPurchase invoicePurchase invoice matchingPurchase orderPurchase requisition.
RE:
These fields (and reports) are part of the NA Localization. The reports in the NA localization that contain the "Print on.." fields do not contain a lot of the newer logic in the Standard (base) reports. They also only have RDLC layouts. These fields should be moved to the W1 app, so all customers can use the comment functionality, and embrace the modern reporting strategy of Word Layouts.
RE:
@moderator: This is solved in 10.0.43, issue 973365 - Unable to change address in Sales line upon changing header address
RE:
Hello, it was planned on 2025 wave 1 and still no information. This is really a must have for event registration formsWill it come and when?
RE:
Great idea!
RE:
Yes please. Larger retailers need to monitor open shifts and ensure they are closed in a timely manner. The ability to see Open Shifts (and specifically filter for Shifts which were opened yesterday and still Open) is required. The only known workaround is to query ShiftIDs from retail transactions table where there is no corresponding Closed Shift
RE:
Pretty please please please! This is such a seemingly simple thing to a customer, though I realize in reality it's not so simple. It would have a good impact on usability.
RE:
For the integration situations would be nice, i can also imagine many copilot interesting scenarios with that.