#12135 Fix Reverse Charge VAT upgrade migration
Corrected field mappings and filtering logic in the Reverse Charge VAT upgrade migration to properly transfer legacy values into new GB fields using type-correct filters.
- 1files
- 1AL files
- 1objects
Pull request · merged into main (BC30) on 2026-10-06 by ventselartur · 1 file (+47 -31), 1 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Fixed reversed source and destination field ID mappings across setup, item, and sales/purchase tables
- Filters now use each source field’s typed default instead of blank text for Boolean and Decimal fields
- Removed the VAT Amount Line transfer and its unused namespace import
- Skips writes when source and target values already match
- Closes the record reference explicitly
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 10554 “Upgrade Reverse Charge VAT”, ReverseChargeVAT (GB layer): modified
Context
- Work items: AB#650031
- Labels: Team: Finance
- Systems: finance
- From the description: “Correct the migration to copy legacy values into the new GB fields using type-correct filters.”
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).