#9430 Fix untrappable JSON error in E-Document ADI import (Bug 640122)
E-Document matching assistance import now handles malformed Azure Document Intelligence responses gracefully by checking JSON property existence and adding telemetry for diagnostic purposes instead of crashing with an untrappable error.
- 1files
- 1AL files
- 1objects
Pull request · merged into main (BC30) on 2026-07-15 by ventselartur · 1 file (+22 -6), 1 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Get calls in GetInnerObject and GetHeaderFields now check the return value before using the token
- Missing ADI response properties (outputs, 1, result, fields) no longer cause untrappable runtime errors
- Helpers return an empty JsonObject when an expected property is absent
- Warning telemetry 0000UK1 to 0000UK4 names the missing property for diagnosis
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 6121 “EDocument Json Helper”, EDocument: modified
Context
- Work items: AB#640122
- Labels: AL: Apps (W1)
- Systems: integration
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).