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…

The problem is that calculations are performed by asynchronous workflows, which run in the background and are not guaranteed to execute immediately. This causes the observed delays. To provide real-time updates, the business logic must be executed synchronously.

A real-time workflow (Option A) is a type of synchronous workflow that runs immediately as part of the same database transaction as the triggering event. Similarly, a synchronous plug-in (Option D) executes immediately and within the transaction. Both options would force the quote total to be recalculated and displayed to the user instantly upon updating a line item, directly resolving the issue.

B. Consolidate multiple asynchronous workflows into a single asynchronous workflow.

This does not address the core problem. The process remains asynchronous and will still execute in the background with a delay, failing to meet the real-time requirement.

C. Implement a business process flow to replace the existing workflows.

Business process flows are designed to guide users through a multi-stage process. They are not the appropriate tool for executing immediate, transactional calculations upon a field change.

---

1. Microsoft Learn | Power Automate Documentation. "Use real-time workflows".

Reference: Under the section "When to use real-time workflows", it states, "Unlike asynchronous workflows, real-time workflows execute immediately... They run in the same transaction as the base operation." This supports using a real-time workflow (Option A) for immediate execution.

2. Microsoft Learn | Dataverse Developer Guide. "Event framework".

Reference: In the section "Synchronous and asynchronous execution", it explains, "A plug-in can be registered to execute synchronously or asynchronously. A synchronous plug-in causes the platform to wait for the plug-in to finish execution before the main operation can continue." This supports using a synchronous plug-in (Option D) for real-time logic.

3. Microsoft Learn | Dataverse Developer Guide. "Asynchronous service in Dataverse".

Reference: The overview section states, "The asynchronous service executes long-running operations like bulk email, workflows, and bulk import, independently of the main Dataverse core operation." This explains why the current asynchronous implementation (and Option B) causes delays.