codeunitPlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Codeunit 1597 "Email Upgrade"

System Application · System.Email

Across versions

  1. BC23-25present
  2. BC263 procedures added
  3. BC27-29unchanged
  4. BC301 procedures added

Neighbourhood 4 connected objects and pages

Codeunit 9999 "Upgrade Tag" (calls, 5 links)Upgrade TagCodeunit 1596 "Email Installer" (calls)Email InstallerCodeunit 8930 "Email View Policy" (calls)Email View PolicyCodeunit 8999 "Email Rate Limit Impl." (calls)Email Rate Limit Impl.

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.

System Application · System.Email · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal
Subtype Upgrade

Event subscriptions

  • RegisterPerCompanyTags subscribes to Codeunit “Upgrade Tag” OnGetPerCompanyUpgradeTags

Procedures

  • GetEmailTablesAddedToAllowedListUpgradeTag(): Code[250] + BC26

Plus 4 local procedures.

Triggers

OnUpgradePerCompany

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.

Recent changes

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: "Email Upgrade"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources