Page 30415 "API IC Incoming Notification"
CrossEnvironmentIntercompany · Microsoft.Intercompany.CrossEnvironment
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 2 connected objects and pages
CrossEnvironmentIntercompany · Microsoft.Intercompany.CrossEnvironment · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | false |
| SourceTable | IC Incoming Notification |
| PageType | API |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| notificationInfo | Id | Operation ID | — |
| Source Intercompany Partner Code | Source IC Partner Code | — | |
| Target Intercompany Partner Code | Target IC Partner Code | — | |
| Notified DateTime | Notified DateTime | — |
Triggers
OnInsertRecord
Relations
- source table Table 613 “IC Incoming Notification”
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” (1 call:
OnInsertRecord → InsertICIncomingNotification)
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: "page", object_name: "API IC Incoming Notification"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.