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

Codeunit 4397 "SOA Test Setup"

SalesOrderAgent · Microsoft.Agent.SalesOrderAgent

Across versions

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

Neighbourhood 4 connected objects and pages

Table 4325 "SOA Setup" (relates to)SOA SetupCodeunit 4400 "SOA Setup" (calls, 5 links)SOA SetupCodeunit 8901 "Email" (calls, 2 links)EmailCodeunit 4396 "SOA Email Setup" (calls)SOA Email Setup

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
Permissions tabledata “Email Inbox” = rd

Procedures

  • SetTestEmailConnection(TestConnection: Boolean)
  • SetTestEmailCount(TestCount: Boolean)
  • EmailConnectionTest(var TempSOASetup: Record "SOA Setup" temporary)
  • EmailCountTest(var TempSOASetup: Record "SOA Setup" temporary)
  • GetEmailCount(): Integer

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

  • Codeunit 4400 “SOA Setup” (5 calls: GetEmailsCount → (object), GetEmailsCount → GetEmailCount, GetEmailsCount → SetTestEmailCount, …)

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

Evidence 1 sources