Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-10-06 07:06:54 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Fix remaining READ-convention sample links across this PR's 18 articles

Browse source 
The same plain-backtick "See sample: \`x.good.al\`." form fixed on
al-methods-limited-during-write-transactions (PR #161) turned up
repo-wide on 15 more of this PR's articles - Knowledge-Retrieval.ps1
requires the markdown-link form to associate a sample with its
article. All 16 fixed; the four local validators (frontmatter,
knowledge-index, knowledge-retrieval, review-fixtures, skill-index)
pass.
This commit is contained in:
Michael Dieringer 2026-09-21 22:30:25 +02:00
parent faa0bceb86
commit b983a6da57
16 changed files with 32 additions and 32 deletions
Download patch file Download diff file Expand all files Collapse all files

4
microsoft/knowledge/data-modeling/check-post-line-batch-pattern.md
View file

@ -19,10 +19,10 @@ Business Central's own journal-based posting routines consistently follow a thre
`Check Line` reads setup/dimension data only on its first call and shows no UI beyond errors. `Post Line` only operates on the record passed to it — never the Journal table — so it can be called directly by other posting code, including a document posting routine. `Post Batch` is the only one of the three that reads and updates the Journal table, and it is the only one invoked from the Post action on a journal page. A `-Post` document codeunit is never called directly from a page; a page calls a `-Post (Yes/No)` confirmation wrapper instead, so the same `-Post` codeunit can also run unattended from a batch-posting report.
See sample: `check-post-line-batch-pattern.good.al`.
See sample: [`check-post-line-batch-pattern.good.al`](check-post-line-batch-pattern.good.al).
## Anti Pattern
A single monolithic posting codeunit that reads the Journal table, validates lines, writes ledger entries, and shows confirmation dialogs all in one procedure. It cannot be reused by another posting routine without fabricating journal records, and it cannot run unattended because it insists on user interaction.
See sample: `check-post-line-batch-pattern.bad.al`.
See sample: [`check-post-line-batch-pattern.bad.al`](check-post-line-batch-pattern.bad.al).