Codeunit 2135 "O365 Setup Email"
Base Application
Across versions
- BC23-30present
Neighbourhood 6 connected objects and pages
Base Application · BC23-30 · source at ea08af5e · facts from BC29
Procedures
SetupEmail(ForceSetup: Boolean)CheckMailSetup()
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 8894 “Email Account” (1 call:
CheckMailSetup → IsAnyAccountRegistered) - Page 8886 “Email Account Wizard” (1 call:
SetupEmail → (object))
Called by
- Codeunit 20038 “APIV1 - Send Sales Document” (3 calls:
SendCancelledCreditMemo → CheckMailSetup,SendDocument → CheckMailSetup,SendPostedCreditMemo → CheckMailSetup) - Codeunit 30038 “APIV2 - Send Sales Document” (3 calls:
SendCancelledCreditMemo → CheckMailSetup,SendDocument → CheckMailSetup,SendPostedCreditMemo → CheckMailSetup) - Page 20012 “APIV1 - Sales Invoices” (3 calls:
SendCanceledInvoice → CheckMailSetup,SendDraftInvoice → CheckMailSetup,SendPostedInvoice → CheckMailSetup) - Page 30012 “APIV2 - Sales Invoices” (3 calls:
SendCanceledInvoice → CheckMailSetup,SendDraftInvoice → CheckMailSetup,SendPostedInvoice → CheckMailSetup)
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: "O365 Setup Email"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.