bcquality/microsoft/knowledge/data-modeling/initialize-document-defaults-in-initrecord.md
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.6 KiB

bc-version domain keywords technologies countries application-area
all
data-modeling
document-header
initrecord
number-series
default-values
oninsert
initialization
al
w1
all

Initialize document defaults in InitRecord after assigning the number

Description

Business Central document headers assign their number series first and then call an InitRecord procedure that owns the remaining business defaults, such as posting and document dates. Keeping that sequence and extensibility point makes initialization consistent for every creation path and lets extensions subscribe around one documented operation. Defaults scattered across page triggers or unrelated helpers can differ between UI, API, test, and background creation.

Best Practice

In the document table's insert path, assign the document number and then call InitRecord. Keep the default assignments in that procedure and expose narrow before/after events when other extensions must participate.

See sample: initialize-document-defaults-in-initrecord.good.al.

Anti Pattern

Assigning document defaults in a page trigger, or scattering them directly through OnInsert with no InitRecord boundary. Non-page creation paths can then miss the defaults, and extensions have no stable initialization hook.

See sample: initialize-document-defaults-in-initrecord.bad.al.

Reference

Use the InitRecord function