Page 1366 "Field Monitoring Setup"
Base Application · System.Diagnostics
Across versions
- BC23-29present
- BC30declaration changed
Neighbourhood 5 connected objects and pages
Base Application · System.Diagnostics · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Field Monitoring Setup |
| Extensible | false |
| SourceTable | Field Monitoring Setup |
| PageType | Card |
| UsageCategory | Administration |
| ApplicationArea | Basic, Suite |
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 | User ID | User Id | Specifies the user ID |
| Notification Email Account | Email Account Name | Specifies the email account that will send the notification email. Typically, this is a system account that is not associated with a user. | |
| General | Monitor Status | Monitor Status | Specifies the monitor status |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Start | Start monitoring fields for changes. | |
| Stop | Stop monitoring fields for changes. | ||
| Retention Policy | View or edit the retention policy. | Page 3901 “Retention Policy Setup Card” |
Triggers
OnOpenPage, OnAfterGetCurrRecord
Relations
- source table Table 1366 “Field Monitoring Setup”
Pages and codeunits on this table
- Table 1366 “Field Monitoring Setup” (lookup page)
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 1392 “Monitor Sensitive Field” (1 call:
OnOpenPage → GetSetupTable)
Called by
- Codeunit 1392 “Monitor Sensitive Field” (1 call:
OpenFieldMonitoringSetup → (object))
Recent changes
- 2026-09-28 #11920 Add title to field monitoring feature pages (main, BC30, feature)
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
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: "Field Monitoring Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.