Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-10-05 14:46:55 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 4
bcquality/microsoft/knowledge/privacy/featuretelemetry-logerror-implicit-errortext.md
Jesper Schulz-Wedde 2b5550c346
Some checks failed
Validate knowledge index / validate-index (push) Has been cancelled
Details
Validate AL review fixtures / validate-review-fixtures (push) Has been cancelled
Details
Validate frontmatter and structure / validate (push) Has been cancelled
Details
Improve partner onboarding and documentation navigation (#174) 
Lead with a complete plugin quick start and add task-oriented usage, troubleshooting, customization, and contribution guides. Preserve the broader plugin framing, correct conflicting contract guidance, support Agents folder reviews, and align repository validation. Convert existing sample references to clickable links without changing knowledge rules.

Co-authored-by: Jesper Schulz-Wedde <jesper.schulzwedde@microsoft.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
2026-09-09 17:31:03 +02:00

1.4 KiB
Raw Blame History

bc-version domain keywords technologies countries application-area
18..
privacy
featuretelemetry
logerror
errortext
errorcallstack
alerrortext
alerrorcallstack
customdimensions
al
w1
all

FeatureTelemetry.LogError emits more than caller custom dimensions

Description

FeatureTelemetry.LogError emits its ErrorText as the telemetry message and adds it as alErrorText. The overloads with ErrorCallStack also add alErrorCallStack. These dimensions are produced in addition to the caller-supplied CustomDimensions dictionary, and the Feature Telemetry implementation sends the event as SystemMetadata.

Best Practice

Review the dedicated error arguments as telemetry payload. Capture GetLastErrorText(true) when scrubbed platform error text is sufficient, and pass GetLastErrorCallStack() only as a call stack. Keep custom dimensions non-personal too.

See sample: featuretelemetry-logerror-implicit-errortext.good.al.

Anti Pattern

Approving a LogError call because its explicit dictionary contains only safe values while it passes unsanitized GetLastErrorText() or arbitrary context through ErrorText or ErrorCallStack. Those arguments become telemetry dimensions outside the dictionary.

See sample: featuretelemetry-logerror-implicit-errortext.bad.al.