#10483 [Subcontracting] Bug 647210 & 647791: Enable IT migration in production and keep Legacy Subcontracting on when app install is declined
The Legacy Subcontracting to Subcontracting app migration now works in production environments, and declining the app installation prompt no longer incorrectly disables the legacy feature.
- 3files
- 2AL files
- 1objects
Pull request · merged into main (BC30) on 2026-09-01 by alexei-dobriansky · 3 files (+95 -66), 2 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Removed sandbox-only restriction preventing production environments from migrating to Subcontracting app
- Fixed issue where declining app installation still disabled Legacy Subcontracting, leaving data stranded
- CheckCanDisableLegacySubcontracting now returns Boolean to properly control whether disabling proceeds
- Removed unused System.Environment import and sandbox-related error label
- Added test case to verify legacy feature stays enabled when app installation is declined
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 99008501 “Legacy Subc. Feature Handler”, Base Application (IT layer): modified
src/Layers/IT/BaseApp/Manufacturing/Setup/ManufacturingSetup.Page.al: modified, not in the BC30 snapshot
Also merged into
- #10760 into
releases/29.xon 2026-08-28
Context
- Work items: AB#647210, AB#647791
- Labels: Ownership: Manual, Subcontracting, Team: SCM
- Systems: manufacturing
- From the description: “Disabling Legacy Subcontracting is now permitted in production when migration prerequisites are met.”
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).