Codeunit 533 "IC New Notification JR"
Base Application · Microsoft.Intercompany.DataExchange
Across versions
- BC23-28present
- BC29declaration changed
- BC30unchanged
Neighbourhood 5 connected objects and pages
Base Application · Microsoft.Intercompany.DataExchange · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Permissions | tabledata “IC Outgoing Notification” = m, tabledata “IC API Log” = rimd |
Procedures
1 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 537 “IC API Log Context” (2 calls:
OnRun → Finalize,OnRun → Initialize) - Codeunit 8703 “Feature Telemetry” (2 calls:
SendNotification → LogError,SendNotification → LogUsage) - Codeunit 428 “IC Mapping” (1 call:
SendNotification → GetFeatureTelemetryName) - Codeunit 560 “CrossIntercompany Connector” (1 call:
SendNotification → SubmitRecordsToICPartnerFromEntityName) - Codeunit 561 “IC Data Exchange API” (1 call:
SendNotification → CreateJsonContentFromICIncomingNotification)
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 New Notification JR"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.