#9438 SL - Add support for migrating historical project transactions
A new migration setting enables historical project transactions to be migrated alongside other historical data during SL migration, making project history a first-class migration option.
- 3files
- 3AL files
- 3objects
Pull request · merged into main (BC30) on 2026-10-02 by blauerPCL (community contribution) · 3 files (+26 -2), 3 AL · feature · tier official · reviewed (checked by Opus)
What changed
- Added ‘Migrate Hist. Project Trans.’ setting in migration configuration UI and per-company settings
- Wired the historical population flow to run project-specific migration when enabled
- Project history follows same control mechanism as GL, AR, AP, inventory, and purchase history
- Processes PJTran, PJTranEx, PJProj, and related project records
- Maintains consistent behavior for ‘enable all historical transactions’ option
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 47025 “SL Populate Hist. Tables”, HybridSL: modified
- Page 47017 “SL Company Add. Settings List”, HybridSL: modified
- Page 47018 “SL Migration Configuration”, HybridSL: modified
Context
- Work items: AB#575742
- Labels: ADO: Sync, AL: Apps (W1), From Fork, Team: Integrations
- 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).