#10492 [SOA] Restrict direct deletion of contact overrides
The SOA Task Contact Override table restricts direct deletion by removing the inherent delete permission, while preserving legitimate deletions through validated code paths.
- 1files
- 1AL files
- 1objects
Pull request · merged into main (BC30) on 2026-08-21 by tomasevicst · 1 file (+1 -1), 1 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Inherent delete permission removed from table to prevent unauthorized direct deletion via RecordRef or similar mechanisms
- Deletion still available through SOA Filters Impl codeunit which validates access before removing records
- Insert, modify, read and contact-routing operations unchanged
- Prevents bypassing contact-mapping authorization checks
- No data migration or backward compatibility issues
- Behaviour changes for users or extensions.
AL objects touched
- Table 4588 “SOA Task Contact Override”, SalesOrderAgent: modified
Context
- Work items: AB#640656
- Labels: AL: Apps (W1), Team: SCM
- Systems: development
- From the description: “Deletion remains available through SOA Filters Impl., which validates access and has direct delete permission.”
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).