Codeunit 1292 "Trace"
Base Application · System.Utilities
Across versions
- BC23-30present
Neighbourhood 5 connected objects and pages
Base Application · System.Utilities · BC23-30 · source at ea08af5e · facts from BC29
Procedures
LogStreamToTempFile(var ToLogInStream: InStream; Name: Text; var TempBlobTraceLog: Codeunit "Temp Blob"): TextLogXmlDocToTempFile(var XmlDoc: DotNet XmlDocument; Name: Text): TextLogTextToTempFile(TextToLog: Text; FileName: Text)
Triggers
OnRun
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 419 “File Management” (5 calls:
LogStreamToTempFile → BLOBExportToServerFile,LogStreamToTempFile → ServerTempFileName,LogTextToTempFile → ServerTempFileName, …) - Codeunit 4100 “Temp Blob” (3 calls:
LogStreamToTempFile → CreateInStream,LogStreamToTempFile → CreateOutStream,LogStreamToTempFile → HasValue)
Called by
- Codeunit 1410 “Doc. Exch. Service Mgt.” (5 calls:
CheckConnection → LogStreamToTempFile,DispatchDocument → LogStreamToTempFile,GetDocDispatchErrors → LogStreamToTempFile, …) - Codeunit 1290 “SOAP Web Service Request Mgt.” (3 calls:
ProcessFaultResponse → LogStreamToTempFile,TraceLogStreamToTempFile → LogStreamToTempFile,TraceLogXmlDocToTempFile → LogXmlDocToTempFile) - Codeunit 1297 “Http Web Request Mgt.” (1 call:
TraceLogStreamToTempFile → LogStreamToTempFile)
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: "Trace"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.