code change · feature · breakingIntegration & APIsofficial - Microsoftreviewed - checked by Opus

#11484 [E-Documents Core] - Supported type direction configuration

E-Document services now support per-document-type direction configuration (Incoming, Outgoing, or Both), allowing administrators to control which document types each service can process and preventing implicit document exchanges.

Pull request · merged into main (BC30) on 2026-09-29 by GediminasGaubys (community contribution) · 19 files (+1248 -93), 15 AL · feature · tier official · reviewed (checked by Opus)

What changed

  • Adds a Direction field (Incoming, Outgoing, Both) to E-Doc. Service Supported Type, backed by the new closed enum E-Doc. Supp. Type Direction
  • Outbound creation, recreate and batch export require Outgoing or Both; V1 and V2 inbound processing require Incoming or Both and log an error otherwise
  • A missing supported-type row now denies both directions; built-in services (PDF reader, ForNAV, Payables Agent, demo) are seeded with Incoming rows
  • Per-company upgrade turns existing rows into Both and missing types into Incoming, except seven fallback-secondary types left unconfigured
  • Uses one lookup for non-fallback types, caches the service record in the V2 rejection path, and fixes recurrent and threshold batch export edge cases
  • Breaking: existing extensions can stop compiling or working.

AL objects touched

Context

  • Work items: AB#650228
  • Labels: ADO: Sync, AL: Apps (W1), From Fork, Team: Integrations
  • Systems: integration, development

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