codeunitCopilot & Agentsofficial - Microsoftderived - from the source, no model text

Codeunit 6938 "EA Agent Dispatcher"

ExpenseAgent · Microsoft.ExpenseAgent

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 13 connected objects and pages

Table 6930 "Expense Agent Setup" (relates to)Expense Agent SetupCodeunit 8703 "Feature Telemetry" (calls, 8 links)Feature TelemetryCodeunit 6940 "EA Retrieve Emails" (calls, 3 links)EA Retrieve EmailsCodeunit 6941 "EA Http Client" (calls, 2 links)EA Http ClientCodeunit 8894 "Email Account" (calls, 2 links)Email AccountCodeunit 457 "Environment Information" (calls)Environment InformationCodeunit 6300 "Azure AD Mgt." (calls)Azure AD Mgt.Codeunit 6935 "EA Agent Scheduler" (calls)EA Agent SchedulerCodeunit 6939 "EA Email Setup" (calls)EA Email SetupCodeunit 7771 "Azure OpenAI" (calls)Azure OpenAICodeunit 8901 "Email" (calls)EmailCodeunit 8904 "Email Message" (calls)Email MessageCodeunit 9005 "Url Helper" (calls)

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.

ExpenseAgent · Microsoft.ExpenseAgent · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal
TableNo Expense Agent Setup

Procedures

  • RunEAAgent(var Setup: Record "Expense Agent Setup")
  • CalcNextRunDateTime(EASetup: Record "Expense Agent Setup"; LastRunAt: DateTime): DateTime (internal)

Plus 20 local procedures.

Triggers

OnRun

Relations

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

Evidence 1 sources