Skip to content

Bug 637527: Set DataClassification = SystemMetadata on PEPPOL 3.0 Setup table#8515

Merged
Groenbech96 merged 1 commit into
mainfrom
magnushar/637527-peppol-data-classification
Jun 8, 2026
Merged

Bug 637527: Set DataClassification = SystemMetadata on PEPPOL 3.0 Setup table#8515
Groenbech96 merged 1 commit into
mainfrom
magnushar/637527-peppol-data-classification

Conversation

@Groenbech96

@Groenbech96 Groenbech96 commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Summary

Move DataClassification to the table level (SystemMetadata) on table 37202 PEPPOL 3.0 Setup. All fields on this table are system metadata (the primary key and two enum format selectors), so the table-level classification is the correct semantic and removes the need for per-field overrides.

Why

Data Classification Eval. Data.CreateEvaluationData only creates Data Sensitivity entries for fields classified as CustomerContent, EndUserIdentifiableInformation, or EndUserPseudonymousIdentifiers. With the previous CustomerContent table-level default inherited by fields 2 and 3, entries were created as Unclassified, causing Data Classs Demo Data Tests.TestDataSensitivities to fail with:

Field 2 of Table 37202 has Data Sensitivity Unclassified

With SystemMetadata at the table level, no entries are created for these fields and the test passes.

Work item

AB#637527

@Groenbech96 Groenbech96 requested a review from a team as a code owner June 8, 2026 07:43
@github-actions github-actions Bot added the AL: Apps (W1) Add-on apps for W1 label Jun 8, 2026
@Groenbech96 Groenbech96 force-pushed the magnushar/637527-peppol-data-classification branch from 96d3248 to 51b5e18 Compare June 8, 2026 07:46
@Groenbech96 Groenbech96 changed the title Classify PEPPOL 3.0 Setup table fields as Normal data sensitivity Set DataClassification on PEPPOL 3.0 Setup format fields Jun 8, 2026
@Groenbech96 Groenbech96 enabled auto-merge (squash) June 8, 2026 08:00
@github-actions github-actions Bot added this to the Version 29.0 milestone Jun 8, 2026
…up table

Move DataClassification to table level (SystemMetadata) since all fields are

system metadata (primary key and enum format selectors). This avoids creating

unclassified Data Sensitivity entries during evaluation data setup, which were

causing the Data Classs Demo Data Tests.TestDataSensitivities test to fail.
@Groenbech96 Groenbech96 force-pushed the magnushar/637527-peppol-data-classification branch from 51b5e18 to 5f8c7e2 Compare June 8, 2026 08:30
@Groenbech96 Groenbech96 changed the title Set DataClassification on PEPPOL 3.0 Setup format fields Bug 637527: Set DataClassification = SystemMetadata on PEPPOL 3.0 Setup table Jun 8, 2026
@Groenbech96 Groenbech96 merged commit 0cc97f3 into main Jun 8, 2026
53 checks passed
@Groenbech96 Groenbech96 deleted the magnushar/637527-peppol-data-classification branch June 8, 2026 12:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AL: Apps (W1) Add-on apps for W1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants