bcquality/microsoft/knowledge/breaking-changes/obsolete-table-fields-instead-of-deleting-them.good.al
Jesper Schulz-Wedde 958b033535 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
2026-07-15 09:19:35 +02:00

17 lines
612 B
AL

table 50310 "Customer Profile Good"
{
fields
{
field(1; "No."; Code[20]) { }
// 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';
}
}
}