Comments
Being able to scan manufacturer coupons and have the POS automatically apply the discount—based on the GS1 barcode—is essential. It avoids manual workarounds, reduces errors, and ensures a smooth customer experience. If we can also import vendor coupon data at HQ to match these barcodes, it will save a lot of time, money, and effort across the board.
Hello, I think it is already possible as soon as you 've code the required barcodes on production documents (ex: production route card). You can scan the job ID into the search bar and enter it automatically. It is also possible to scan the production order ID so you've got the full jobs list. What kind of scanning are you expecting?
Strong support for this feature. The lack of a pre-InitReport trigger severely limits our ability to programmatically influence the request page — even for something as basic as loading user-specific filter presets.As a result, we’re forced into fragile workarounds (custom wrappers, extra launch pages, etc.), which feel unnecessary for what should be a clean solution.Adding OnBeforeInitReport() would allow developers to deliver personalized report experiences that persist across sessions and users, without needing to rewrite standard report workflows. This is a high-impact, low-footprint enhancement.
I naturally assumed this would be a feature introduced with the addition of interfaces.I too would like this feature, because interfaces are functionally a "CodeunitRef", so it makes perfect sense to need to bind event subscriptions for them, it would also represent a performance increase due to the toggling off of event subscribers for interface implementation codeunits.This feature's absence is extremely limiting.