codeunitAL Developmentofficial - Microsoftderived - from the source, no model text

Codeunit 2135 "O365 Setup Email"

Base Application

Across versions

  1. BC23-30present

Neighbourhood 6 connected objects and pages

Codeunit 20038 "APIV1 - Send Sales Document" (calls, 3 links)APIV1 - Send Sales DocumentCodeunit 30038 "APIV2 - Send Sales Document" (calls, 3 links)APIV2 - Send Sales DocumentPage 20012 "APIV1 - Sales Invoices" (calls, 3 links)APIV1 - Sales InvoicesPage 30012 "APIV2 - Sales Invoices" (calls, 3 links)APIV2 - Sales InvoicesCodeunit 8894 "Email Account" (calls)Email AccountPage 8886 "Email Account Wizard" (calls)Email Account Wizard

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.

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.

Called by

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.

Evidence 1 sources