Comments
Please, this is badly needed. The current work-around is to duplicate the current tab, then click the item you want. Sometimes it takes like 30 seconds for the duplicated tab to open and I forget what I was trying to click by then. This seems to be the only web-based app that does not have this functionality.
This is very needed (and should be simple) feature to add. It gives a very strong customer bad experience. Especially from customers migrating from older version. We constantly need to handle this "negative" side and hear "It supposed to be new system with improved UX". Please add this feature. It should be a quick win.
Technical Analysis: The root cause appears to be linked to the MCRBrokerCommission records generated from the POS channel. Key findings include: The MarkUpTransRecID field in these records is not populated, leading to erroneous zero values in the broker charge display methodology. A method in the Retail Call stack, specifically RetailTransactionServiceOrder::createMarkupTrans(), deletes the existing MarkupTrans record and fails to re-establish the relationship with the MCRBrokerCommission record, unlike in the Call Center order process where the record is retained.
We are experiencing a critical issue related to broker contracts and claims specifically when Retail Sales Orders are generated from the POS channel. While functionality operates correctly for orders made via the HQ Call Center channel—with proper broker claims being generated—orders from the POS channel fail to reflect accurate broker charges or create broker claims, severely impacting our compliance with vendor agreements and our perception as an omnichannel retailer. Issue Details: POS Channel Orders: When a Retail Sales Order is generated through the retail statement posting of the POS channel, a broker charge record is created but consistently displays a value of zero. Despite identical customer, item, and quantity details with the Call Center orders, no corresponding broker claim is generated. Business Justification: This inconsistency undermines our agreements with vendors, as we cannot claim to uphold broker contracts for some transaction channels while disregarding others. Such discrepancies inhibit our ability to represent D365 Commerce as a true omnichannel solution.
Hi all,Sorry for the late reply on this. It appears this was mis-posted to the Customer Insights - Data, but you're actually speaking about a feature in Customer Insights - Journeys.This was not picked up as CI-Data removed its consent feature many years back, so the ideas folder was not actively being monitored. Sorry about that.I'll loop in the right folks that work on CI-J Consent.