Adjust audit log tables

[Wael (WaelAbuSeada)]

Remove audit log tables

Fixes AB#646814

[github-actions]

Issue #646814 is not valid. Please make sure you link an issue that exists, is open and is approved.

[github-actions]

$\textbf{🟡\ Medium\ Severity\ —\ Breaking\ Changes}$

This change stops treating four Financial Report tables ("Financial Report User Filters", "Financial Report Export Log", "Fin. Rep. Package Export Log", "Financial Report Audit Log") as always-logged in Change Log Management, so customers or dependent customizations that rely on automatic audit entries for those tables will silently stop receiving new entries going forward. If that behavioral change is intended (e.g. avoiding recursive logging of log/export tables), it should be documented; otherwise these tables should remain in the always-logged list.

Line mapping was unavailable, so this was posted as an issue comment.

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.32.4}

[github-actions]

$\textbf{🟡\ Medium\ Severity\ —\ Security}$

This change removes "Financial Report Audit Log", "Financial Report Export Log", and "Fin. Rep. Package Export Log" from the always-logged table set in the OnAfterIsAlwaysLoggedTable subscriber. In Change Log Management, always-logged tables bypass normal Change Log activation/setup checks, so this turns tamper-evident logging for audit/export records into an optional administrator configuration instead of a guaranteed one. Because these tables are still modifiable/deletable per the codeunit's own permission grant (tabledata "Financial Report Audit Log" = ri) and related permission sets, a user with modify/delete rights on these tables could alter or delete audit-relevant history without guaranteed change-log evidence going forward. If the intent was to avoid redundant self-logging of the audit/export tables, confirm that decision explicitly (e.g., in the PR description) since it weakens tamper-evidence for compliance-sensitive log data; otherwise keep these tables in the always-logged list or add an equivalent mandatory tamper-evident logging mechanism.

_{Agent judgement — not directly backed by a BCQuality knowledge article.}

Line mapping was unavailable, so this was posted as an issue comment.

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.32.4}

[alexei-dobriansky]

Agentic PR Review - Round 1

Recommendation: Accept with Suggestions

What this PR does

This PR removes four tables from the always-logged set in the Financial Report Auditing codeunit (8390) - the OnAfterIsAlwaysLoggedTable subscriber on Change Log Management. The removed tables are Financial Report User Filters, Financial Report Export Log, Fin. Rep. Package Export Log, and Financial Report Audit Log.

The change is coherent. The four table objects still exist; they are only dropped from the "always logged" change-log set, so this is a behavior change, not compile cleanup. Removing the two export-log tables and the audit-log table from change logging is reasonable, since they are high-volume log tables and change-logging the audit log itself is redundant - the codeunit still stamps the audit log through its own OnBeforeInsert handler and still registers its retention policy. Financial Report User Filters is per-user UI state, so auditing it adds noise. The remaining configuration tables stay always-logged.

Suggestions

S1 - Add a regression test for the logged-table set
This changes which Financial Report tables are always written to the Change Log, and it is a BaseApp change that reaches every tenant. Add a small test that calls the OnAfterIsAlwaysLoggedTable path and asserts the four removed tables are no longer always-logged while the kept ones still are. This locks the intended behavior so a later edit to the list does not silently re-add them.

Risk assessment and necessity

Risk: Low to moderate. No posting, amount, or ledger logic is touched. The compatibility point is that changes to these four tables will no longer appear in Change Log Entries; a tenant that relied on change-log history for financial-report export or filter tables would lose that trail. This is a BaseApp change, so it applies to all tenants. The audit log keeps its own entries and retention policy, so its core function is unaffected.

Necessity: The change is needed to stop change-logging log and per-user state tables that should not be audited, reducing Change Log noise and storage. The scope is narrow and targeted - only the always-logged list is edited.

---

[AI-PR-REVIEW] version=1 promptVersion=2 system=github pr=10252 round=1 by=alexei-dobriansky at=2026-08-17T01:15:42.5410863Z lastSha=30975cfb45433a9da76da889cebfa8ea3138644c reviewKey=na suggestions=S1@7e3c1a96