Codeunit 1420 "Doc. Exch. Serv.- Doc. Status"
Base Application · Microsoft.EServices.EDocument
Across versions
- BC23-24present
- BC253 events added, 2 procedures removed
- BC26-30unchanged
Neighbourhood 5 connected objects and pages
Base Application · Microsoft.EServices.EDocument · BC23-30 · source at ea08af5e · facts from BC29
Events published
OnDocExchStatusDrillDown(var DocRecRef: RecordRef; var Handled: Boolean)(integration)OnBeforeCheckAndUpdateDocExchStatus(var DocRecRef: RecordRef; var IsHandled: Boolean)+ BC25 (integration)- subscribers: Codeunit 6468 “Serv. Doc. Exchange Mgt.” OnBeforeCheckAndUpdateDocExchStatus
OnAfterIsSupportedByDefaultDocExchStatusDrillDown(DocRecRef: RecordRef; var IsSupported: Boolean)+ BC25 (integration)- subscribers: Codeunit 6468 “Serv. Doc. Exchange Mgt.” OnAfterIsSupportedByDefaultDocExchStatusDrillDown
OnAfterCheckPostedDocs()+ BC25 (integration)- subscribers: Codeunit 6468 “Serv. Doc. Exchange Mgt.” OnAfterCheckPostedDocs
Procedures
DocExchStatusDrillDown(DocRecVariant: Variant)
Plus 5 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 1411 “Doc. Exch. Links” (4 calls:
CheckAndUpdateDocExchStatus → CheckAndUpdateDocExchCrMemoStatus,CheckAndUpdateDocExchStatus → CheckAndUpdateDocExchInvoiceStatus,CheckPostedCrMemos → CheckAndUpdateDocExchCrMemoStatus, …) - Codeunit 701 “Data Type Management” (2 calls:
DefaultDocExchStatusDrillDown → FindFieldByName,DocExchStatusDrillDown → GetRecordRef) - Codeunit 10 “Type Helper” (1 call:
DefaultDocExchStatusDrillDown → GetOptionNo) - Codeunit 1410 “Doc. Exch. Service Mgt.” (1 call:
DefaultDocExchStatusDrillDown → GetExternalDocURL)
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. Serv.- Doc. Status"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.