Preserve published field IDs in sample

Keep the existing Email and Contact Email field IDs unchanged, clarify that the sample represents an independent baseline, and use a local breaking-change rule for the generic smoke evaluation.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 9825b012-e653-496a-9310-c1f4b6f8ac27
This commit is contained in:
Jesper Schulz-Wedde 2026-07-15 09:19:35 +02:00
parent f76279057e
commit 958b033535
2 changed files with 6 additions and 7 deletions

View file

@ -8,8 +8,7 @@
"context": "AppSourceCop mandatoryAffixes is configured to ABC."
},
"breaking-changes": {
"article": "obsolete-table-fields-instead-of-deleting-them",
"context": "Baseline version: field ID 2 was named Email. Review the provided changed version."
"article": "do-not-expose-sensitive-data-through-public-api"
},
"events": {
"article": "initialize-ishandled-to-false-before-publishing"

View file

@ -3,15 +3,15 @@ table 50310 "Customer Profile Good"
fields
{
field(1; "No."; Code[20]) { }
// Old field kept and marked Pending so dependent code keeps compiling and
// an upgrade codeunit can copy its data before it is finally removed.
field(2; "Email"; Text[80])
// Replacement field receives a new ID in this independent example.
field(2; "Contact Email"; Text[80]) { }
// Old field keeps its original ID and is marked Pending so dependent code
// keeps compiling while an upgrade codeunit migrates its data.
field(3; "Email"; Text[80])
{
ObsoleteState = Pending;
ObsoleteReason = 'Replaced by Contact Email. Will be removed after the deprecation window.';
ObsoleteTag = '25.0';
}
// Replacement field shipped under a new ID alongside the old one.
field(3; "Contact Email"; Text[80]) { }
}
}