#11992 Fix IRS Forms statement filters for box codes containing parentheses
IRS Forms statement filters now handle box codes with parentheses correctly by treating form-box identifiers as literal values instead of filter syntax.
- 4files
- 3AL files
- 3objects
Pull request · merged into main (BC30) on 2026-09-29 by ventselartur · 4 files (+48 -6), 3 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Added SetFormBoxFilter method to build literal filters using SetRange instead of text interpolation
- Updated upgrade and setup statement creation to use the new setter method
- Preserves existing metadata, insertion behavior, and upgrade guards
- Resolves statement creation and data upgrade failures caused by parentheses in box codes
- Added regression test covering parentheses in form-box codes
- Behaviour changes for users or extensions.
AL objects touched
- Table 10041 “IRS 1099 Form Statement Line”, IRSForms (US layer): modified
- Codeunit 10058 “IRS 1099 Upgrade”, IRSForms (US layer): modified
- Codeunit 10039 “IRS Forms Data”, IRSForms (US layer): modified
Also merged into
- #12182 into
releases/29.xon 2026-10-08
Context
- Work items: AB#651660
- Labels: Team: Finance
- Systems: finance
- From the description: “Programmatically generated filters should treat the form-box identifier as a literal value rather than filter syntax.”
Source: metadata of a merged pull request in microsoft/BCApps (bcapps): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).