Page 1368 "Monitor Field Setup Wizard"

Base Application · System.Diagnostics · captioned “Field Monitoring Assisted Setup Guide” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Field Monitoring Assisted Setup Guide
PageType	NavigatePage

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
In Progress Banner	MediaResourceStandardReference	`MediaResourcesStandard."Media Reference"`	—
Welcome	For each change, you can view the original and new value, the user who made the change, and the time and date that the change occurred.	label	—
	Monitoring fields can impact performance. We recommend that you only monitor the fields you think are most important.	label	—
Let’s Get Started	If you have not classified your fields, you can add fields and manage settings for individual fields on the Monitored Fields Worksheet page.	label	—
	OpenDataClassificationWorksheetMsg	`OpenDataClassificationWorksheetMsg`	Opens Data Classification Worksheet
	Sensitive	`ImportSensitiveFields`	Specifies whether to add fields that have a Sensitive data sensitivity classification.
	Personal	`ImportPersonalFields`	Specifies whether to add fields that have a Personal data sensitivity classification.
	Company Confidential	`ImportCompanyConfidentialFields`	Specifies whether to add fields that have a Company Confidential data sensitivity classification.
Choose The Change Notification Recipient	Notification Recipient	`MonitorUserId`	Specifies the username of the person to notify about a change in a monitored field.
EmailAccount	Notification Email Account	`EmailAccountName`	Specifies the email account that will send the notification email. Typically, this is a system account that is not associated with a user.
Permission Warning	The selected user can receive email notifications about changes to field values. To allow the user to address changes you must assign the D365 Monitor Fields permission set to them.	label	—
	Do you want to do that now?	`OpenUserCardMsg`	Opens User page for the selected user
Done Banner	MediaResourceDoneReference	`MediaResourcesDone."Media Reference"`	—
That’s it!	View Monitored Fields	`OpenMonitorWorksheetPage`	Open the Monitored Fields Worksheet to review your settings when finished.

Actions

Group	Action	ToolTip
Processing	Back	Go to previous page
	Next	Go to next page
	Finish	Finish the wizard

Procedures

4 local procedures, no public ones.

Triggers

OnInit, OnOpenPage

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” (5 calls: OnOpenPage → GetSetupTable, OnOpenPage → ValidateUserPermissions, ValidateAndFinishSetup → EnableMonitor, …)
Codeunit 1990 “Guided Experience” (1 call: ValidateAndFinishSetup → CompleteAssistedSetup)
Codeunit 4030 “Client Type Management” (1 call: LoadTopBanners → GetCurrentClientType)
Codeunit 8714 “Audit Log” (1 call: ValidateAndFinishSetup → LogAuditMessage)
Codeunit 8894 “Email Account” (1 call: OnOpenPage → IsAnyAccountRegistered)
Page 1369 “Monitored Fields Worksheet” (1 call: ValidateAndFinishSetup → (object))
Page 8886 “Email Account Wizard” (1 call: OnOpenPage → (object))

Called by

Codeunit 1392 “Monitor Sensitive Field” (1 call: OpenFieldMonitoringSetupWizard → (object))

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: "Monitor Field Setup Wizard"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.