Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-08-06 09:26:52 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Align field obsoletion sample baselines

Browse source 
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
This commit is contained in:
Jesper Schulz-Wedde 2026-07-15 09:34:57 +02:00
parent 26f7cb72a8
commit edf2d653c8
1 changed files with 3 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

5
microsoft/knowledge/breaking-changes/obsolete-table-fields-instead-of-deleting-them.bad.al
View file

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