Codeunit 4420 "SOA Task Message Reader"
SalesOrderAgent · Microsoft.Agent.SalesOrderAgent
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 2 connected objects and pages
SalesOrderAgent · Microsoft.Agent.SalesOrderAgent · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
| Permissions | tabledata “Agent Task Message” = r, tabledata “Agent Task Message Attachment” = r |
Procedures
GetLastIncomingMessageContent(AgentTaskID: BigInteger): Text(internal)AppendAttachmentContent(AgentTaskMessage: Record "Agent Task Message"; var MessageContent: Text)(internal)
Plus 1 local procedures.
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.
- Codeunit 4312 “Agent Session” (2 calls:
GetLastIncomingMessageContent → GetCurrentSessionAgentTaskId,GetLastIncomingMessageContent → IsAgentSession)
Called by
- Codeunit 4591 “SOA Item Search” (1 call:
GetTaskMessageContent → GetLastIncomingMessageContent)
Recent changes
- 2026-08-05 #9364 Slice 622414: [SOA] [Pioneer] Enhancing Sales Order Agent with Item Variant : availability and prices (main, BC30, feature, added)
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 Task Message Reader"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.