bcquality/microsoft/knowledge/breaking-changes/obsolete-table-fields-instead-of-deleting-them.good.al
Jesper Schulz-Wedde e81632b4be Complete AL review knowledge readiness
Fill telemetry and Query coverage, strengthen thin review domains, correct audited content defects, and add deterministic cheap-model evaluation and reference-integrity safeguards.

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

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

17 lines
618 B
AL

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])
{
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]) { }
}
}