Page 655 "IC Outgoing Notifications"
Base Application · Microsoft.Intercompany.DataExchange
Across versions
- BC23-28not present
- BC29added
- BC30unchanged
Neighbourhood 1 connected objects and pages
Base Application · Microsoft.Intercompany.DataExchange · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | IC Outgoing Notifications |
| SourceTable | IC Outgoing Notification |
| PageType | List |
| UsageCategory | None |
| ApplicationArea | Intercompany |
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 |
|---|---|---|---|
| Notifications | Operation ID | Operation ID | Specifies the unique identifier of the notification. |
| Source IC Partner Code | Source IC Partner Code | Specifies the IC partner that sent this notification. | |
| Target IC Partner Code | Target IC Partner Code | Specifies the IC partner that should receive this notification. | |
| Status | Status | Specifies the current processing status of this notification. | |
| Notified DateTime | Notified DateTime | Specifies when the notification was sent or last processed. | |
| Error Message | ErrorMessageText |
Specifies the error message if the notification failed. |
Triggers
OnAfterGetRecord
Relations
- source table Table 612 “IC Outgoing Notification”
Ask your agent
Procedure bodies are not stored here (D10). 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: "IC Outgoing Notifications"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.