#146 knowledge: three false-positive guards from BCApps PR 10277, 10278 and 10346
Three BCQuality knowledge articles were added or updated to stop false positives: insert-only transfers that rely on the caller to clean up first, member affixes in apps that do not configure an AppSourceCop mandatory affix, and permission tests that lower the context through a composed role. Genuine defects remain reportable.
- 3files
- 3AL files
- 0objects
Pull request · merged into main on 2026-09-02 by gggdttt · 3 files (+34 -6), 3 AL · fix · tier official · reviewed (checked by Opus)
What changed
- New article clarifies that insert-only transfers are safe when the caller’s OnValidate trigger cleans up the target range first
- AppSource affix requirement now correctly scoped to apps with AppSourceCop enabled and configured with mandatory affix
- Permission test guidance refined to recognize effective permission context through role composition, not just direct permission set assignment
- All three false positives were verified against actual BCApps code before writing the rules
- Genuine defects remain reportable: missing cleanup with different filters or reachable paths without cleanup
AL objects touched
microsoft/knowledge/appsource/two-level-namespace-replaces-object-affix-not-extension-member-affix.md: modified, not in the BC? snapshotmicrosoft/knowledge/data-modeling/insert-only-transfer-may-rely-on-caller-cleanup.md: added, not in the BC? snapshot yetmicrosoft/knowledge/testing/permission-tests-must-lower-the-execution-context.md: modified, not in the BC? snapshot
Context
- Systems: development
- From the description: “Three false-positive guards adjudicated from self-improvement runs on BCApps PR 10277, 10278 and 10346.”
Source: metadata of a merged pull request in microsoft/BCQuality (bcquality): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).