Codeunit 1411 "Doc. Exch. Links"

Base Application · Microsoft.EServices.EDocument · BC23-30 · source at ea08af5e · facts from BC29

Properties

Events published

• OnBeforeUpdateDocumentRecord(DocRecRef: RecordRef; DocIdentifier: Text; DocOrigIdentifier: Text; var IsHandled: Boolean) (integration)
  • subscribers: Codeunit 6468 “Serv. Doc. Exchange Mgt.” OnBeforeUpdateDocumentRecord

Procedures

• UpdateDocumentRecord(DocRecRef: RecordRef; DocIdentifier: Text; DocOrigIdentifier: Text)
• CheckAndUpdateDocExchCrMemoStatus(SalesCrMemoHeader: Record "Sales Cr.Memo Header")
• CheckAndUpdateDocExchInvoiceStatus(SalesInvoiceHeader: Record "Sales Invoice Header")

Plus 4 local procedures.

Triggers

OnRun

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

• Codeunit 1410 “Doc. Exch. Service Mgt.” (2 calls: CheckAndUpdateDocExchCrMemoStatus → GetDocumentStatus, CheckAndUpdateDocExchInvoiceStatus → GetDocumentStatus)

Called by

• Codeunit 1420 “Doc. Exch. Serv.- Doc. Status” (4 calls: CheckAndUpdateDocExchStatus → CheckAndUpdateDocExchCrMemoStatus, CheckAndUpdateDocExchStatus → CheckAndUpdateDocExchInvoiceStatus, CheckPostedCrMemos → CheckAndUpdateDocExchCrMemoStatus, …)
• Codeunit 1410 “Doc. Exch. Service Mgt.” (2 calls: DispatchDocument → UpdateDocumentRecord, SendUBLDocument → UpdateDocumentRecord)

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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: "Doc. Exch. Links"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.