Issue 29317

[Bertverbeek4PS]

Summary

The field 'Amount to Review' will now be filled when the page is opened with the calculated field remaining amount.

Work Item(s)

Fixes #29317

Fixes AB#615546

[Copilot]

Pull request overview

This PR addresses issue #29317 by auto-filling the "Amount to Review" field with the calculated remaining amount when records are displayed on the Review G/L Entries page.

Key Changes:

• Auto-populates "Amount to Review" field when it's zero using the RemainingAmount calculation in the OnAfterGetRecord trigger

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.

[Copilot]

Modifying Rec."Amount to Review" in OnAfterGetRecord without persisting it to the database can lead to inconsistent behavior. The CalcBalance() function (lines 402-412) iterates through all records and sums "Amount to Review", but it will only see persisted values, not the in-memory modifications made in this trigger. This means the Balance calculation may be incorrect when records have their "Amount to Review" auto-filled but not explicitly modified by the user.

Consider either:

1. Persisting the change by calling Rec.Modify() after setting the value, or
2. Updating CalcBalance() to account for auto-filled values that haven't been persisted

Suggested change

	if Rec."Amount to Review" = 0 then
	Rec."Amount to Review" := RemainingAmount;
	if Rec."Amount to Review" = 0 then begin
	Rec."Amount to Review" := RemainingAmount;
	if not Rec.IsNew() then
	Rec.Modify();
	end;

[Copilot]

The new auto-fill behavior for "Amount to Review" lacks test coverage. Since the repository includes comprehensive test coverage for this page (see ReviewGLEntriesTests.Codeunit.al), a test should be added to verify that:

1. When "Amount to Review" is 0, it gets auto-filled with RemainingAmount
2. When "Amount to Review" is non-zero, it remains unchanged
3. The auto-filled value is correctly used in subsequent operations

[github-actions]

Processing this PR. The branch is now locked 🔒 Please don't push updates unless otherwise agreed.