[AI Test Toolkit] Refresh Run History when changing View By

[onbuyuka]

Summary

On the AI Eval Suite Run History page (page 149032 "AIT Run History"), changing the View By control (Version/Tag) — or toggling Apply Filter — did not update the displayed data.

Root cause

Two compounding defects in the refresh path:

1. Repaint. UpdateRunHistory() rebuilds the temporary source table (DeleteAll + re-Insert inside codeunit 149036 "AIT Run History".GetHistory) and then calls the parameterless CurrPage.Update(), which defaults to Update(true). That tries to save the (just-deleted) current record rather than redraw. The canonical pattern after repopulating a temporary page source is CurrPage.Update(false).

2. Stale FlowFilter. GetHistory set the "Line No. Filter" FlowFilter only when LineNo <> 0 and never cleared it. Since DeleteAll does not clear filters, unchecking Apply Filter (LineNo -> 0) left the previous line filter on the FlowFields, so the columns recomputed against the wrong line and showed zeros/old data.

Fix

• AITRunHistory.Page.al — CurrPage.Update(false) after rebuilding the temp records.
• AITRunHistory.Codeunit.al — clear the "Line No. Filter" FlowFilter when LineNo = 0 (add an else SetRange("Line No. Filter")).

Impact / risk

Low — internal AI Test Toolkit tooling page, read-only temporary source. Both changes are the standard idioms for this scenario.

Verification

• Statically traced: View By OnValidate → UpdateRunHistory → GetHistory (sole data builder) → CurrPage.Update. FlowField columns key on "Line No. Filter".
• ⚠️ Not runtime-verified on an NST (AL does not run locally here) — relying on PR CI for compile + tests; manual repro on the Run History page recommended before merge.

Linked work item: AB#622420

🤖 Generated with Claude Code

[onbuyuka]

CI note: the Clean build failure is a known BCApps incremental-build infra issue — not this change

The ... (Clean) build failure is not caused by this PR. The incremental Clean build compiles the modified AI Test Toolkit app against the System Application bundled in the BC platform artifact (sandbox/29.0.51094.0) instead of the freshly-built System Application. That artifact predates #8381, which added Agent Task.OpenAgentTaskLogEntries / GetStepsDoneCount (called by AITAgentLogEntryPart.Page.al), so the compiler reports AL0132 ... does not contain a definition for ....

Evidence it is infrastructure, not this change:

• The Default build of this same app passes (compiles against fresh symbols).
• main`s full build passes (System Application compiled from source).
• The two methods exist, unwrapped (present under CLEAN29), in current main source and in the last-green baseline a97db24da.
• PRs that modify System Application (e.g. [Azure AD Plan] Update access for GDAP users who were previously guests #8441, [Retention Policy] Keep record marks for indirect-permission subset deletes #8469) pass Clean because they rebuild it from source; only AI-Test-Toolkit-only PRs hit this.
• Build log shows the Clean compile resolving Microsoft_System Application.app from the BcContainerHelper compiler-folder cache (the platform artifact), not the freshly-built 29.0.74476.0.

No code change is appropriate (a #if not CLEAN29 guard on non-obsolete methods would be wrong). This goes green once the platform-artifact pin advances past #8381. Holding for that.