Page 6758 "Reminder Act. History Detailed"
Base Application · Microsoft.Sales.Reminder
Across versions
- BC23not present
- BC24added
- BC25-30unchanged
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Sales.Reminder · BC24-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| SourceTable | Reminder Action Group Log |
| PageType | Document |
| ApplicationArea | All |
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 |
|---|---|---|---|
| General | Run Id | Run Id | Specifies the identifier of the run. |
| Reminder Action Group | Reminder Action Group ID | Specifies the reminder action group. | |
| StartedCompletedGroup | Started on | Started On | Specifies when the job was started. from the table field |
| Completed on | Completed On | Specifies when the job was completed. from the table field | |
| NumberOfErrorsGroup | Number of errors | NumberOfErrors |
Specifies the number of errors that occurred during the run. |
| Content | Action log | part Page 6757 “Reminder Act. History Log” | — |
Triggers
OnAfterGetCurrRecord
Relations
- source table Table 6753 “Reminder Action Group Log”
Pages and codeunits on this table
- Page 6756 “Reminder Action History” (card page)
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: "Reminder Act. History Detailed"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.