Comments
This idea closely aligns with challenges we are experiencing when using Advanced Warehouse Management in D365, particularly with our FEFO location directive logic / work header breaks.In environments where inventory is stored in shared locations full or partial pallets with product of the same batch, D365 currently is consolidating those license plates into a single Work ID when are released our work to the warehouse. This behavior breaks the expected relationship between what our physical pallets and the system work as it wants us to pick partials under 1 Work ID that exceeds the item pallet quantity or quantities. Our use case highlights the need for work header breaks by License Plate IDs to function consistently when inventory is stored in the same location with the same batch.From an outbound perspective, the desired system behavior is:FEFO based on expiration dateFull pallets prioritized before partial palletsPartial pallets kept as separate work and license plates, never merged Consistent logic across live load and pick-to-stage flowsExclusion of inventory in non-released batch status or non-pickable locations (staging, trailers, WIP)While location directives and work templates can enforce FEFO and full vs. partial pallet logic independently, the system does not reliably create separate work headers per license plate, creating an immense roadblock for us to implement a FEFO strategy for our operations. Enhancing standard D365 functionality to better support license-plate-level work header breaks would significantly benefit not only us, but potentially other customers operating in similar warehouse footprints. We strongly support this idea and believe it would be a valuable addition to the product roadmap.
Scope clarification: In addition to enabling updates to the Shopify variant Title, we request four IntegrationEvents in the Shopify Connector to allow clean customization of variant option formatting and safe field preservation during sync:OnAfterFillInProductVariantData (ShpfyProductExport) after standard fields are set, before the temp variant is consumed (lets us format Option values and Title with full context of Item/ItemVariant/Shop).OnBeforeAssignTempVariantToDbRecord (ShpfyVariantAPI) immediately before ShopifyVariant := TempShopifyVariant; (last chance to adjust temp or prepare DB to preserve selected fields).OnBeforeSetVariantOptionValues (ShpfyProductExport) gives granular control to completely replace option value formatting logic.OnAfterUpdateVariantsAssignment (ShpfyVariantAPI) just after assignment, before modify/post steps (three‑way context for selective field preservation/audit). Business benefit: These events avoid brittle table‑level interception, reduce sync time on large catalogs (>50k variants), and make variant naming/extensibility predictable.
No, we don't work with Segments. The Idea is: We have an Event in 6 month and have just one Journey: 1st Touchpoint: Someone registeres for the Event and receives an confirmation via a trigger based journey (event registration trigger)2nd Touchpoint: 2 days before the event e reminder is sent out with a Link to Teams Event (online event) or QR Code etc. (non online events)
It is very important to have control over ones own deployments when it comes to performance. Waiting for Microsoft tickets is unacceptable. Microsoft teams have preached that PPAC will have parity to LCS or they haven't done their job. It is no where near parity.....more like parody in that it's comical the lack of tools we have for F&O environments. App Insights is lacking and barely gives enough details without doing ones own custom telemetry.
