5 AL/BC patterns: document distribution (Report Selections, Document Sending Profile, Find Entries, TransferFields) - #175
Open
Michael Dieringer (MichaelDieringer) wants to merge 1 commit into
Conversation
…ent Sending Profile, Find Entries, TransferFields) Five rules about Business Central's document distribution architecture, verified against BCApps source and Microsoft Learn. - custom-document-dispatch-must-not-bypass-report-selections - document-print-and-email-actions-call-report-selections-directly - extend-find-entries-navigate-for-new-document-types - extend-report-selection-usage-for-new-document-types - transferfields-mirrored-fields-must-match-type-and-length Wired into al-data-modeling-review.md's worklist cues. Added a disambiguation note on the TransferFields article distinguishing it from the existing transferfields-skip-type-mismatch-can-drop-data.md (type-mismatch skipping vs. length mismatch, which SkipFieldsNotMatchingType does not affect). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Michael Dieringer (MichaelDieringer)
requested a review
from Jesper Schulz-Wedde (JesperSchulz)
as a code owner
September 10, 2026 05:44
Author
|
@microsoft-github-policy-service agree company="CURABIS ApS" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Five rules about Business Central's document distribution architecture, verified against BCApps source and Microsoft Learn:
Report Selectionsloses per-account layout overrides and "Document Layouts" discoverability.Report Selectionsdirectly;Document Sending Profileis scoped specifically to the combined Post-and-Send action, not general print/email.page 344 Navigate) requires bothOnAfterFindRecordsandOnBeforeShowRecords; either alone leaves a result row with nothing to open it.Report Selection Usagevalue needs bothReportSelections.InsertRecordand a subscriber to the Customer/Vendor "Document Layouts" filter events, or the per-account override UI never lists the new document type.TransferFieldsposting cascade (e.g.Sales Header→Sales Invoice Header) must match type and length exactly; a length-only mismatch compiles and posts cleanly until a value finally exceeds the shorter definition.Each article cites specific BCApps source (file, procedure, and in most cases line number) and, where applicable, Microsoft Learn. Wired into
al-data-modeling-review.md's worklist cues so all five are reachable in review. Added a disambiguation note on the TransferFields article distinguishing it from the existingtransferfields-skip-type-mismatch-can-drop-data.md— that article coversSkipFieldsNotMatchingTypemasking a type mismatch; this one covers the length dimension, which that parameter does not affect at all.Test plan
🤖 Generated with Claude Code