[MAIN]-Bug 644801-IRS Reporting Period - Copy Setup process will copy the 1099 Adjustments as part of the process of copying from one IRS Reporting Period to a new Period setup.

[v-praghav]

What & why

Issue: Copy Setup was incorrectly carrying 1099 adjustment amounts from source period to target period.

Cause: The copy logic duplicated the full adjustment record, including the Amount field, instead of resetting it for the new period.

Linked work

AB#644801

Fixes #
Solution: Update copy logic to explicitly set Amount = 0 before insert in target period, and add an automated test to validate this behavior during setup copy.

How I validated this

• I read the full diff and it contains only changes I intended.
• I built the affected app(s) locally with no new analyzer warnings.
• I ran the change in Business Central and confirmed it behaves as expected.
• I added or updated tests for the new behavior, or explained below why none are needed.

What I tested and the outcome (required — be specific: scenarios, commands, screenshots for UI changes)

Risk & compatibility

[github-actions]

$\textbf{🟠\ High\ Severity\ —\ Testing}$

CopySetupMessageHandler is an empty [MessageHandler] with no Enqueue/Dequeue verification, so the new test VendorFormBoxAdjustmentAmountIsResetWhenCopyingSetup only proves that some Message(...) call was raised during CopyPeriodSetup. It never asserts the expected message text (e.g. via LibraryVariableStorage.Enqueue/Dequeue and Assert.ExpectedMessage) or that it fired the expected number of times, so the test would stay green even if the wrong message, or an unexpected extra message, were shown.

Knowledge:

• microsoft/knowledge/testing/ui-handlers-in-tests.md

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