mirror of https://github.com/microsoft/BCQuality.git synced 2026-10-05 14:46:55 +01:00

Jesper Schulz-Wedde 8f025ac679 Merge current main into development guidance

Reconcile the read-only guidance output with the machine-readable skill index,
adopt linked sample references required by bounded retrieval, and update the
guidance regression fixture for the retrieval helper dependency. Permit only
the known endpoint-DLP metadata stream during read-only evidence capture.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 638b66d2-9f06-4f60-8781-808709e1485c

2026-09-18 12:04:06 +02:00

1.5 KiB

Raw Blame History

bc-version

domain

keywords

technologies

countries

application-area

all

upgrade

install-codeunit

upgrade-codeunit

execution-order

subtype-install

subtype-upgrade

sequencing

all

Separate install or upgrade codeunits have no execution order

Description

An extension can contain multiple Install or Upgrade codeunits, but Business Central does not guarantee the order in which codeunits of the same subtype execute. Upgrade trigger phases are ordered globally, yet one codeunit's OnUpgradePerCompany must not assume another codeunit's same-phase trigger already ran. Object ID and source-file order do not provide sequencing.

Best Practice

Keep separate install or upgrade codeunits independent. When two steps have a real dependency, coordinate them from one owning trigger in the required order; use upgrade tags to make each completed step idempotent.

See sample: install-and-upgrade-codeunits-have-no-order.good.al.

Anti Pattern

Splitting dependent steps into separate codeunits and relying on names, object IDs, or declaration order. The dependent codeunit can run first and fail or observe partially migrated data.

See sample: install-and-upgrade-codeunits-have-no-order.bad.al.

Reference

Create proper installation and upgrade codeunits

1.5 KiB Raw Blame History