BC Observatoryunofficial, made by waldo
codeunitIntegration & APIsofficial - Microsoftderived - from the source, no model text

Codeunit 6408 "E-Doc. PEPPOL DX Post-Mapping"

EDocument · Microsoft.eServices.EDocument.Processing.Import

Open in Claude6408.mdSource on GitHub

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 1 connected objects and pages

Table 1220 "Data Exch." (relates to)Data Exch.

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

EDocument · Microsoft.eServices.EDocument.Processing.Import · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal
TableNo Data Exch.

Procedures

4 local procedures, no public ones.

Triggers

OnRun

Relations

Ask your agent

Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "codeunit", object_name: "E-Doc. PEPPOL DX Post-Mapping"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources