#9363 GP - Updates 202607
The GP migration now spreads item transactions across multiple batches instead of one and supports more custom G/L account expense categories. Validation is corrected for payment terms, POs split over multiple lines, and Code/Text type mismatches, and the account beginning balance validation is removed for now.
- 8files
- 8AL files
- 8objects
Pull request · merged into main (BC30) on 2026-09-11 by jaymckinney-enavate (community contribution) · 8 files (+110 -197), 8 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Item transactions are distributed across multiple batches instead of a single batch
- Support added for additional custom G/L account expense categories
- Validation fixed for payment terms and for POs whose items are split over multiple lines
- Code versus Text type mismatches in validation corrected, for example postal code
- Account beginning balance validation removed pending a redesign
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 40032 “Migration Validation”, HybridBaseDeployment: modified
- Codeunit 4019 “GP Item Migrator”, HybridGP: modified
- Table 4024 “GP Configuration”, HybridGP: modified
- Codeunit 4037 “Helper Functions”, HybridGP: modified
- Codeunit 40903 “GP Migration Validator”, HybridGP: modified
- Page 4051 “GP Company Add. Settings List”, HybridGP: modified
- Page 40056 “GP Company Migration Settings”, HybridGP: modified
- Page 4050 “GP Migration Configuration”, HybridGP: modified
Context
- Work items: AB#624473
- Labels: ADO: Sync, AL: Apps (W1), From Fork, Team: Integrations
- Systems: development
- From the description: “A single item batch was being created, when transactions should have been distributed among multiple”
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).