Comments
Agreed! The issue described here is that real-time marketing currently checks the "Do Not Allow Bulk Email" field as part of the consent process. Suppose a customer updates their contact information using the preference center page. In that case, their contact point consent records will be updated, but the "Do Not Allow Bulk Email" field will not be updated. This could result in a customer receiving marketing messages even though they have opted out of receiving them. This would be a great OOB feature.
For us, we are seeing the need for a cancelled order in FnO to adjust the softreserve measure in IV. The situation is we have is using IOM, with IV - inventory source from FnO. In FnO, "manual" reservation is configured. Orders first land in FnO, then once confirmed, this triggers the IOM orchestration. In IOM, the soft reserve action is made to IV which adjusts the softreserve measure, sends reservation id to FnO through dual-write. Works great. Our issue is on cancelled orders in FnO. Once confirmed, if an order is cancelled in FnO, it does not adjust the softreserve measure in IV. Like it does when the pick list is registered. It feels like the cancelled event in FnO, needs to adjust the softreserve measure in IV in a similar fashion. Thank you.
Dear Microsoft Product Group team, Possibility to modify date and exchange rate on expense with per-diem category is highly demanded customer requirement form different countries. In case of Expense management, localization requirements are not fulfilled at all, but making date/rate editable would cover part of this. It's a pity that Expense does not have such possibility, especially when across other forms this things are possible to change.Even in Expenses, we can change that for other category types. Can You maybe plan this for one of next releases, maybe in 10.0.39?
To add to this, using an ingestion rule is not an ideal solution. We are currently blocking all Sandbox uptake with an ingestion rule... It leaves no room for adding Sandbox data to telemetry on-the-fly for specific scenarios where you may need it. Having the option to 'Cherry-Pick' which sandboxes upload telemetry data would be nice.