Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-08-06 17:36:53 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
bcquality/microsoft/knowledge/privacy/error-vs-message-telemetry-logging.md
Jesper Schulz-Wedde aca3986fd0
Correct security and privacy knowledge guidance (#92) 
* Correct security and privacy guidance

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 9c2eebc4-dcd5-4b85-8113-90772d818900

* Address security privacy review findings

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 9c2eebc4-dcd5-4b85-8113-90772d818900

---------

Co-authored-by: Jesper Schulz-Wedde <jesper.schulzwedde@microsoft.com>
2026-07-14 11:25:03 +02:00

1.2 KiB
Raw Permalink Blame History

bc-version domain keywords technologies countries application-area
20..
privacy
error
message
confirm
notification
telemetry
logging
ui-dialog
al
w1
all

Error dialogs emit Error method trace telemetry

Description

When Error displays a dialog, Business Central emits the RT0030 Error method trace telemetry signal. Message, Confirm, and Notification do not emit that Error method trace signal. For RT0030, the actual AL error string is included only when the first Error argument is a Label or TextConst; other first-argument types produce generic guidance instead of the dynamic string.

Best Practice

Use a Label or TextConst as the direct first argument to Error so telemetry contains a stable, classified message. Review user-facing substitution values for UI appropriateness. Do not treat Message, Confirm, or Notification content as though it were automatically copied into RT0030.

Anti Pattern

Claiming that every rendered Error string is written verbatim to telemetry, or that Message, Confirm, and Notification automatically feed the Error method trace. Both overstate the platform behavior.