A company is implementing Dynamics 365 Sales. The company has turned off out-of-the-box quote calculations in order to implement its own custom calculations. When users update a line item on a…

Question

Options

• AConsolidate asynchronous workflow into a single real-time workflow.
• BConsolidate multiple asynchronous workflows into a single asynchronous workflow.
• CImplement a business process flow to replace the existing workflows.
• DConvert the asynchronous workflows to a synchronous plug-in.

• A
  57% (30)
• B
  13% (7)
• C
  30% (16)

Explanation

The root cause is that asynchronous processes run in a background queue and can be delayed by minutes or hours depending on server load, which is why users see stale totals. Both solutions fix this by making execution synchronous: Option A replaces async workflows with a real-time (synchronous) workflow that executes inline within the same transaction before the response is returned to the user. Option D converts the logic to a synchronous plug-in, which runs within the platform event pipeline and completes before the record save is acknowledged. Consolidating into a single async workflow (B) does not fix the timing problem - it is still asynchronous. A business process flow (C) guides users through stages but does not perform calculations.

No community discussion yet for this question.