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
This commit is contained in:
Jesper Schulz-Wedde 2026-07-14 10:51:12 +02:00
parent 7a678d1aff
commit bc8686d871
31 changed files with 199 additions and 103 deletions

View file

@ -1,16 +1,17 @@
codeunit 50220 "Upgrade New Field Init"
codeunit 50220 "Upgrade Trigger Aware"
{
Subtype = Upgrade;
local procedure InitializeNewFlagOnMyTable()
local procedure UpdateCustomerCreditLimit()
var
MyTable: Record "My Table";
DT: DataTransfer;
Customer: Record Customer;
begin
// "New Flag" is added in the same change as this upgrade procedure.
// No existing validation logic depends on it, so DataTransfer is safe.
DT.SetTables(Database::"My Table", Database::"My Table");
DT.AddConstantValue(true, MyTable.FieldNo("New Flag"));
DT.CopyFields();
if Customer.FindSet(true) then
repeat
// Validate runs the field OnValidate logic; Modify(true) separately
// runs the table OnModify trigger and its row-based events.
Customer.Validate("Credit Limit (LCY)", 50000);
Customer.Modify(true);
until Customer.Next() = 0;
end;
}