bcquality/microsoft/knowledge/breaking-changes/obsolete-table-fields-instead-of-deleting-them.good.al
Jesper Schulz-Wedde 26f7cb72a8 Clarify published field identity rules
State explicitly that a published field keeps its ID, name, and type while a replacement is added as a separate field under an unused ID.

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

Copilot-Session: 9825b012-e653-496a-9310-c1f4b6f8ac27
2026-07-15 09:29:18 +02:00

17 lines
625 B
AL

table 50310 "Customer Profile Good"
{
fields
{
field(1; "No."; Code[20]) { }
// Replacement is a separate field under an otherwise unused ID.
field(2; "Contact Email"; Text[80]) { }
// Old field keeps its original ID, name, and type 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';
}
}
}