Codeunit 534 "IC Read Notification JR"

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

Properties

Procedures

5 local procedures, no public ones.

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 561 “IC Data Exchange API” (4 calls: CleanupNotifications → CreateJsonContentFromICOutgoingNotification, GetICInboxTransaction → PopulateICInboxTransactionFromJson, ReadNotification → EnqueueAutoAcceptedICInboxTransaction, …)
• Codeunit 428 “IC Mapping” (3 calls: CleanupNotifications → GetFeatureTelemetryName, LogError → GetFeatureTelemetryName, ReadNotification → GetFeatureTelemetryName)
• Codeunit 537 “IC API Log Context” (3 calls: LogIncomingNotification → RecordLogEntry, OnRun → Finalize, OnRun → Initialize)
• Codeunit 8703 “Feature Telemetry” (3 calls: CleanupNotifications → LogUsage, LogError → LogError, ReadNotification → LogUsage)
• Codeunit 560 “CrossIntercompany Connector” (2 calls: CleanupNotifications → NotifyICPartnerFromBoundAction, ReadNotification → RequestICPartnerICOutgoingNotification)
• Codeunit 43 “Language” (1 call: ReadNotification → GetDefaultApplicationLanguageId)

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