bcquality/microsoft/knowledge/breaking-changes/obsolete-table-fields-instead-of-deleting-them.bad.al
Jesper Schulz-Wedde edf2d653c8 Align field obsoletion sample baselines
Use Email field ID 3 as the shared baseline so the bad example demonstrates a same-ID rename while the good example retains the original field and adds a separate replacement.

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

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

12 lines
477 B
AL

table 50311 "Customer Profile Bad"
{
fields
{
field(1; "No."; Code[20]) { }
// Breaking: the published Email field at ID 3 was renamed while retaining
// the ID. The good example keeps Email at ID 3 and adds a separate field.
// AppSourceCop AS0005 rejects the compatibility change; retaining the ID
// does not by itself mean the stored column was dropped and re-created.
field(3; "Contact Email"; Text[80]) { }
}
}