---
id: change/bcquality/131
type: change
title: "#131 Correct table-level data classification guidance"
summary: 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.
tier: official
language: en
tags:
  - fix
  - main
system: development
review:
  state: reviewed
  by: opus
  at: "2026-10-08T02:08:40.738Z"
  flags: []
generated:
  at: "2026-10-08T01:26:53.141Z"
  pipeline: 0.2.0
  prompts:
    extract-change: 1
  input_hash: 841b4e7cab84756b680b66328c2f1ceaae3ec892
evidence:
  - kind: code
    url: https://github.com/microsoft/BCQuality/pull/131
    title: "microsoft/BCQuality#131: Correct table-level data classification guidance"
    date: "2026-08-18"
    commit: 841b4e7cab84756b680b66328c2f1ceaae3ec892
    t: null
    quote: null
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
  changes: []
number: 131
repo: microsoft/BCQuality
source_id: bcquality-prs
url: https://github.com/microsoft/BCQuality/pull/131
kind: pr
base_branch: main
major: null
merged_at: "2026-08-18T07:43:37Z"
author: gggdttt
author_type: User
community_contribution: false
labels: []
change_class: code
change_kind: fix
behavior_change: false
breaking: false
files:
  count: 3
  additions: 28
  deletions: 11
  al: 3
apps: []
objects_touched: []
objects_unjoined:
  - path: microsoft/knowledge/privacy/data-classification-required-on-pii-fields.md
    status: modified
    reason: not-in-snapshot
  - path: microsoft/knowledge/privacy/table-level-data-classification-cascades.good.al
    status: modified
    reason: not-in-snapshot
  - path: microsoft/knowledge/privacy/table-level-data-classification-cascades.md
    status: modified
    reason: not-in-snapshot
obsoletions: []
backports: []
fixes_issues: []
work_items: []
systems:
  - development
quote: null
joined_against:
  major: null
  commit: null
---

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

[Pull request](https://github.com/microsoft/BCQuality/pull/131) · 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).