Page 592 "Change Log Setup"

Base Application · System.Diagnostics · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Change Log Setup
SourceTable	Change Log 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
GeneralColumn	Change Log Activated	Change Log Activated	Specifies that the change log is active.
	IMPORTANT	label	—
	Tracking changes can impact performance, which can cost you time, and increase the size of your database, which might cost you money. To reduce those costs, consider the following:	label	—
	- Use caution when choosing the tables and operations.	label	—
	- Do not add ledger entries and posted documents. Instead, prioritize system fields such as Created By and Created Date.	label	—
	- Do not use the All Fields tracking type. Instead, choose Some Fields and track only the most important fields.	label	—

Actions

Group	Action	ToolTip	Runs
Setup	Tables	View what must be logged for each table.
	Retention Policy	View or Edit the retention policy.	Page 3901 “Retention Policy Setup Card”

Procedures

2 local procedures, no public ones.

Triggers

OnOpenPage, OnClosePage

Relations

source table Table 402 “Change Log Setup”

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 27 “Confirm Management” (1 call: ConfirmActivationOfChangeLog → GetResponseOrDefault)
Codeunit 457 “Environment Information” (1 call: ConfirmActivationOfChangeLog → IsSaaS)

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