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

Codeunit 4581 "SOA Send Replies"

SalesOrderAgent · Microsoft.Agent.SalesOrderAgent

Across versions

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

Neighbourhood 7 connected objects and pages

Table 4325 "SOA Setup" (relates to)SOA SetupCodeunit 4418 "SOA Reply Retry Mgt." (calls, 5 links)SOA Reply Retry Mgt.Codeunit 8703 "Feature Telemetry" (calls, 4 links)Feature TelemetryCodeunit 4400 "SOA Setup" (calls, 2 links)SOA SetupCodeunit 4586 "SOA Dispatcher" (calls, 2 links)SOA DispatcherCodeunit 4408 "SOA Set Reply Failed" (calls)SOA Set Reply FailedCodeunit 4419 "SOA Send Reply" (calls)SOA Send Reply

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.

SalesOrderAgent · Microsoft.Agent.SalesOrderAgent · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal
TableNo SOA Setup

Procedures

  • GetAllSentSuccessfully(): Boolean

Plus 6 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.

Called by

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

Evidence 1 sources