#10151 Fix vendor contact relation read permission
Vendor changes made through indirect permissions no longer fail when the contact update check reads Contact Business Relation. VendCont-Update now elevates read permission on that table, and CustCont-Update and BankCont-Update get the same small edit.
- 3files
- 3AL files
- 3objects
Pull request · merged into main (BC30) on 2026-08-13 by PredragMaricic · 3 files (+6 -3), 3 AL · fix · tier official · reviewed (checked by Opus)
What changed
- VendCont-Update now has read permission on Contact Business Relation
- Fixes vendor modification failing for users with only indirect Vendor permissions
- CustCont-Update and BankCont-Update are also modified with the same small edit
- Users need no extra direct permissions; the contact synchronization logic itself is unchanged
- No automated test added; modeled on the existing CustVendBank-Update permission pattern
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 5058 “BankCont-Update”, Base Application: modified
- Codeunit 5056 “CustCont-Update”, Base Application: modified
- Codeunit 5057 “VendCont-Update”, Base Application: modified
Context
- Work items: AB#617469
- Labels: Team: SCM
- Systems: crm
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).