#10828 Avoid remote attachment checks during FactBox refresh

Pull request · merged into main (BC30) on 2026-09-15 by JesperSchulz · 8 files (+301 -36), 3 AL · performance · tier official · reviewed (checked by Opus)

What changed

External-only attachments now rely on persisted metadata for HasContent() checks instead of making synchronous FileExists calls
Removed automatic external provider calls from FactBox refreshes and metadata validation scenarios
Export and preview operations now fail explicitly when external files are missing or account mappings are unconfigured
Expense Agent content-hash updates made best-effort to avoid blocking writes on transient retrieval failures
Added comprehensive test coverage for configured/unconfigured external storage, internal attachments, and retrieval failure scenarios
Behaviour changes for users or extensions.

AL objects touched

Codeunit 6989 “Expense Attachment Mgt.”, ExpenseAgent: modified
Codeunit 8751 “DA External Storage Impl.”, External Storage - Document Attachments: modified
Codeunit 8754 “DA Feature Telemetry”, External Storage - Document Attachments: modified

Also merged into

#11529 into releases/29.x on 2026-09-16

Context

Fixes: #10824 [Bug]: External SharePoint attachments make the document attachment FactBox block list navigation (closed)
Work items: AB#648447
Labels: ADO: Sync, AL: Apps (W1), AL: System Application, Ownership: Needs Review, Team: Other
Systems: development
From the description: “Treat a coherent external-only attachment state as available content based on persisted metadata, matching the metadata-only behavior used for internally stored attachments.”

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).