How to Write a Good Success Message

Success messages confirm user actions in Business Central by reassuring users that tasks like posting invoices or importing orders were completed. Well-designed success messages build trust, boost confidence, and create a professional experience while preventing users from doubting their actions.

Key points

Success messages reassure users their actions completed successfully and prevent doubt when confirmation is absent
Effective messages should be concise, specific (include record numbers or quantities), use past tense, and guide users to next steps
Messages should be consistent across the system with a professional tone, avoiding technical jargon and generic phrases
Use GuiAllowed to prevent messages from showing in background tasks or non-UI scenarios

Quotes

“Without positive feedback, users often assume the worst. That is human nature.” (Explains the psychological basis for why success messages are essential even when systems function correctly)
“Success messages are more than just a formality. They are a key part of building user trust and creating a seamless experience.” (Emphasizes that success messages deserve the same attention as error handling in UX design)
“Use the GuiAllowed property to check whether the user interface is available before displaying any messages.” (Provides technical guidance for preventing errors when messages are triggered in non-interactive contexts)

Context

Features: success messaging, user confirmation, feedback design, GuiAllowed property, message consistency, progress dialogs

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