Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-10-05 14:46:55 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 4
bcquality/microsoft/knowledge/upgrade/check-only-triggers-do-not-migrate-data.md
Jesper Schulz-Wedde b6da405376 Improve partner onboarding and documentation navigation 
Lead with a complete plugin quick start and add task-oriented usage, troubleshooting, customization, and contribution guides. Preserve the broader plugin framing, correct conflicting contract guidance, support Agents folder reviews, and align repository validation. Convert existing sample references to clickable links without changing knowledge rules.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
2026-09-09 17:25:29 +02:00

1.3 KiB
Raw Blame History

bc-version domain keywords technologies countries application-area
all
upgrade
on-check-preconditions
on-validate-upgrade
on-upgrade
read-only-check
data-migration
al
w1
all

Upgrade check triggers do not migrate data

Description

OnCheckPreconditionsPerCompany/PerDatabase run before the upgrade to verify that it can start. OnValidateUpgradePerCompany/PerDatabase run after upgrade logic to verify that it succeeded. Treat both phases as read-only checks. The OnUpgradePerCompany/PerDatabase phase is where the platform expects actual data transformation.

Best Practice

Have check triggers call query-only helpers that raise an error when an invariant fails. Put every Insert, Modify, Delete, Rename, DataTransfer, and other migration write behind helpers called from the matching OnUpgrade... trigger.

See sample: check-only-triggers-do-not-migrate-data.good.al.

Anti Pattern

Repairing data in OnCheckPreconditions... or finishing migration in OnValidateUpgrade.... Those writes blur the phase contract and make a check alter the state it is supposed to assess.

See sample: check-only-triggers-do-not-migrate-data.bad.al.