Drag and Drop Question You are a Dynamics 365 Finance developer. A long running process times out in the system. You need to implement the asynchronous framework to resolve this issue. Which class…

Question

Exhibit

Answer Area

Explanation

Dynamics 365 Finance: Asynchronous Framework - runAsync Class Selection

Background

In D365 Finance (X++), the asynchronous framework lets you offload long-running processes to avoid session timeouts. Two key classes expose a runAsync method: Global and FormRun. Choosing between them depends on whether the operation requires a form/UI context.

The Two Classes Explained

Arrangement Breakdown

Placement 1 → Global Used when the async operation runs independently of any form. Global::runAsync spawns a new server-side session with no UI dependency. Typical use: triggering a background calculation or data process from a non-form context (e.g., service class, batch trigger).

Placement 2 → FormRun Used when the async operation needs access to the calling form's context - for example, reading form datasource records or updating form controls after completion. FormRun::runAsync preserves the form session so UI interaction remains valid.

Placement 3 → Global Again server-side, no form context. This reinforces that Global::runAsync is the general-purpose async launcher when the operation is purely business logic with no UI involvement.

Common Mistakes

• Using FormRun for server-only tasks: Unnecessary overhead; form context isn't available in all execution environments.
• Using Global when UI updates are needed: The async callback won't have access to form controls, causing runtime errors or silent failures.
• Assuming Global means "global scope": In this context it refers to the Global kernel class and its static runAsync method, not a variable scope concept.

Key Rule of Thumb

If the async operation touches the UI or form data, use FormRun::runAsync.
For everything else (pure logic, server-side), use Global::runAsync.

No community discussion yet for this question.