Codeunit 537 "IC API Log Context"

Base Application · Microsoft.Intercompany.DataExchange · BC29-30 · source at ea08af5e · facts from BC29

Properties

Events published

• RecordLogEntryEvent(PartnerCode: Code[20]; DirectionValue: Option; MethodValue: Text; Uri: Text; RequestContent: Text; ResponseContent: Text; StatusCodeValue: Integer; var Handled: Boolean) (integration)
  • subscribers: Codeunit 537 “IC API Log Context” OnRecordLogEntry

Event subscriptions

• OnRecordLogEntry subscribes to Codeunit “IC API Log Context” RecordLogEntryEvent

Procedures

• Initialize()
• Finalize()
• RecordLogEntry(PartnerCode: Code[20]; DirectionValue: Option; MethodValue: Text; Uri: Text; RequestContent: Text; ResponseContent: Text; StatusCodeValue: Integer)

Called by

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 534 “IC Read Notification JR” (3 calls: LogIncomingNotification → RecordLogEntry, OnRun → Finalize, OnRun → Initialize)
• Codeunit 533 “IC New Notification JR” (2 calls: OnRun → Finalize, OnRun → Initialize)
• Codeunit 560 “CrossIntercompany Connector” (1 call: Send → RecordLogEntry)

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: "IC API Log Context"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.