#10819 [Pmt. Recon. Journal] Re-fire OnAfterGetLedgEntryInfo on proposal fast path
The OnAfterGetLedgEntryInfo event is re-fired during payment proposal creation on the fast path after a prior performance refactor accidentally stopped raising it.
- 2files
- 2AL files
- 2objects
Pull request · merged into main (BC30) on 2026-08-31 by dcenic · 2 files (+24 -1), 2 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Re-fires OnAfterGetLedgEntryInfo event for Customer, Vendor, Employee, and Bank Account entries
- Uses a temporary round-trip mechanism without additional ledger reads
- Restores event subscriptions that update proposal fields
- Low risk change that restores pre-refactoring behavior
- Behaviour changes for users or extensions.
AL objects touched
- Table 1294 “Applied Payment Entry”, Base Application: modified
- Table 1293 “Payment Application Proposal”, Base Application: modified
Context
- Work items: AB#648382
- Labels: Team: Finance
- Systems: finance
- From the description: “Re-fire the legacy event via a temp round-trip (no second ledger read) so existing subscribers keep updating proposal fields.”
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).