Progress Dialog: Making Business Central Responsive

Progress Dialog provides user feedback during long-running ERP tasks in Business Central, reducing uncertainty and duplicate actions. This post explains when to use Progress Dialog, shows AL code examples, and provides seven best practices for writing clear, confidence-building progress messages.

Key points

Progress Dialog prevents user frustration and duplicate entries by showing that a process is running and indicating its progress
Use Progress Dialog for tasks taking more than a few seconds, processing many records, or involving multiple steps
Effective progress messages are specific, show counts or percentages, update at meaningful milestones, and include a success message at the end
Poor Progress Dialog implementation with vague messages, too many updates, or overuse can become an obstacle rather than a help

Quotes

“A 1-minute task with feedback feels fine. A 1-minute task without feedback feels broken.” (This captures why Progress Dialog is essential for user trust and perceived system responsiveness)
“Show progress, and slow tasks feel faster.” (This summarizes the core value of implementing Progress Dialog in ERP workflows)

AL objects mentioned

As named in the post. A name that matches one object page by exact type and name links to it; the others stay as named.

other “Dialog”

Context

Features: Progress Dialog, User feedback during processing, Task status indication, Progress tracking with counts or percentages, Multi-step task visualization

Source: That NAV Guy, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.