BC Observatoryunofficial, made by waldo
code change · fixAL Developmentofficial - Microsoftreviewed - checked by Opus

#131 Correct table-level data classification guidance

Privacy guidance now states that a valid table-level DataClassification is inherited by fields unless they override it. The fixture and related PII article were updated to separate inherited defaults from genuinely unclassified fields, which should stop false-positive review comments asking for redundant field-level declarations.

Open in Claude131.mdPull request #131

Pull request · merged into main on 2026-08-18 by gggdttt · 3 files (+28 -11), 3 AL · fix · tier official · reviewed (checked by Opus)

What changed

  • Fields inherit a valid table-level DataClassification unless they override it
  • Companion .good.al fixture and PII article updated to distinguish inherited defaults from unclassified fields
  • Old guidance caused 19 false-positive privacy comments on a BCApps PR
  • Findings are kept for fields whose inherited classification is missing or wrong
  • Behavior checked against AppSourceCop rule AS0016

AL objects touched

  • microsoft/knowledge/privacy/data-classification-required-on-pii-fields.md: modified, not in the BC? snapshot
  • microsoft/knowledge/privacy/table-level-data-classification-cascades.good.al: modified, not in the BC? snapshot
  • microsoft/knowledge/privacy/table-level-data-classification-cascades.md: modified, not in the BC? snapshot

Context

  • Systems: development

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).