#10451 [Bug 647233] Fix User Confirmed copied into Canceled when posting expense report lines
Fixed a data corruption bug where the User Confirmed field from expense report lines was being incorrectly copied into the Canceled field of posted expense report lines during posting, by introducing a new non-colliding field and adding data migration logic.
- 4files
- 3AL files
- 3objects
Pull request · merged into main (BC30) on 2026-08-24 by v-rohangarg20 · 4 files (+119 -3), 3 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Field 92 is User Confirmed on Expense Report Line but Canceled on Posted Expense Report Line, so TransferFields copied confirmation into Canceled
- Canceled (field 92) is obsoleted as Pending and replaced by new field 94 Is Canceled
- Cancel Posted Expense Report now uses Is Canceled
- Upgrade code in UpgradeExpenseAgentSetup migrates existing Canceled data to the new field
- Regression test checks that posting a confirmed line does not mark the posted line canceled
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 6974 “Cancel Posted Expense Report”, ExpenseAgent: modified
- Table 6916 “Posted Expense Report Line”, ExpenseAgent: modified
- Codeunit 6978 “Upgrade Expense Agent Setup”, ExpenseAgent: modified
Obsoletions
- Posted Expense Report Line: Canceled, replaced by Is Canceled
Context
- Work items: AB#647233
- Labels: AL: Apps (W1), Team: Finance
- Systems: development
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).