#9280 Project Task Billing Method reverts to original value in project card without validation or error
Project Task Billing Method field now persists correctly when changed from One Customer to Multiple Customers, fixing a race condition that previously caused the value to revert without error.
- 2files
- 1AL files
- 1objects
Pull request · merged into main (BC30) on 2026-07-14 by tomasevicst · 2 files (+88 -0), 1 AL · fix · tier official · reviewed (checked by Opus)
What changed
- A Modify() call in the OnValidate trigger ensures the updated billing method value is persisted to the database before the platform refreshes the page
- The fix guards against unnecessary modifications by checking if the value actually changed using xRec comparison
- Three test cases validate the core fix, the early-exit path when no tasks exist, and prevention of redundant Modify() calls
- Behaviour changes for users or extensions.
AL objects touched
- Table 167 “Job”, Base Application: modified
Context
- Work items: AB#639677
- Labels: Team: SCM
- Systems: projects
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).