bcquality/microsoft/knowledge/breaking-changes/obsolete-table-fields-instead-of-deleting-them.bad.al
Jesper Schulz-Wedde bc8686d871 Fix lifecycle compatibility guidance
Correct high-confidence Business Central guidance and samples for upgrade tags, collectible errors, trigger semantics, obsoletion, events, interfaces, API contracts, and test transactions.

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

Copilot-Session: e05a43e7-6448-4d67-9c73-798523f5d945
2026-07-14 10:51:12 +02:00

11 lines
386 B
AL

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