bcquality/microsoft/knowledge/breaking-changes/obsolete-table-fields-instead-of-deleting-them.bad.al
Jesper Schulz-Wedde 6140a52b03
Add breaking-changes knowledge domain and review leaf skill (#44)
Seed a new breaking-changes (AL API stability) knowledge domain with six
articles plus good/bad AL samples, a new al-breaking-changes-review leaf
skill, and minimal wiring into al-code-review and the README.

Co-authored-by: Jesper Schulz-Wedde <jesper.schulzwedde@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-06-25 12:33:30 +02:00

11 lines
363 B
AL

table 50311 "Customer Profile Bad"
{
fields
{
field(1; "No."; Code[20]) { }
// Breaking: the published "Email" field was renamed in place. Dependent
// extensions that reference "Email" stop compiling, and the data stored in
// the old column is orphaned on upgrade.
field(2; "Contact Email"; Text[80]) { }
}
}