#12463 Fix Email upgrade writing during no-transaction upgrade test
Email Installer no longer re-registers email tables based on allowed-table row presence, only checking upgrade tags or forced refresh to prevent unwanted database writes during upgrade tests.
- 1files
- 1AL files
- 1objects
Pull request · merged into main (BC30) on 2026-10-07 by darjoo · 1 file (+1 -3), 1 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Removes the IsAllowedTable trigger that caused unnecessary registration of email tables
- Registration now only occurs when upgrade tags are missing or on forced refresh
- Prevents Retention Policy Log Entry writes that violated no-transaction test requirements
- Tag-based behavior from previous change remains intact
- Users can still refresh allowed tables manually via Retention Policy Setup
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 1596 “Email Installer”, System Application: modified
Context
- Work items: AB#651131, AB#652334
- Labels: AL: System Application, 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).