#10162 Fix stale start status in e-document import pipeline
The e-document import pipeline now uses the initial processing status instead of the post-undo status for telemetry emission and event triggering, fixing an edge case where no telemetry or event was sent after undoing to unprocessed.
- 1files
- 1AL files
- 1objects
Pull request · merged into main (BC30) on 2026-08-13 by mynjj · 1 file (+4 -3), 1 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Changed telemetry emit guard to use initial status before undo operations
- Modified OnAfterProcessIncomingEDocument event to use initial status instead of current status
- Fixes edge case where undoing to unprocessed state prevented telemetry and events from being emitted
- Improves code quality by maintaining consistent status usage
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 6140 “E-Doc. Import”, EDocument: modified
Context
- Work items: AB#646592
- Labels: Team: Integrations
- Systems: integration
- From the description: “Use the initial (pre-undo) processing status instead of the post-undo CurrentStatus for both the telemetry emit guard and the OnAfterProcessIncomingEDocument event.”
Source: metadata of a merged pull request in microsoft/BCApps (bcapps): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).