Comments
If I understand correctly, you've setup a workflow where you have multiple approvers getting the same approval notification at the same time, but only 1 person needs to approve. If this was the case, you had to alter the standard condition and made the step where the document is released to Always run. The problem here is that the standard response expects the pending approval condition to be zero hence it doesn't run a critical step "Approve the approval request for the record." What this step does is, it'll go through each open approval entry for the record and close them out as if approved. This same step will also notify the approver that the record has been approved. Edit your workflow and add the missing step to the line where the release document resides and you should be good to go.
Hi Laura,If you're using workflow user groups to do this, then what you're asking for might be doable. Simply give the 3rd approval step users the same sequence, so they can all receive the notification at the same time. Change the final condition from Pending Approvals: 0 to 1, assuming there are only 3 left who must approve, and 2 out of the 3 must approve which will leave you with 1. In the Response for this step, add an "Approve the approval request for the record.". This will find and approve the remaining approvals. If you have 5, for example, and you need 3 out of 5 to approve, then set the Pending Approvals value to 2.
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.