Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-08-06 17:36:53 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Promote performance knowledge from community to Microsoft layer (#50)

Browse source 
Pure git-mv relocation of all 7 performance articles from community/knowledge/performance/ to microsoft/knowledge/performance/. No content changes.

Co-authored-by: Jesper Schulz-Wedde <jesper.schulzwedde@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
Jesper Schulz-Wedde 2026-07-01 10:41:01 +02:00 • committed by GitHub
parent 24e62f5ec8
commit 292bdabe27
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
20 changed files with 0 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

28
microsoft/knowledge/performance/load-only-primary-key-fields-for-reference-work.md Normal file
View file

@ -0,0 +1,28 @@
---
bc-version: [all]
domain: performance
keywords: [setloadfields, primary-key, reference, existence-check, memory]
technologies: [al]
countries: [w1]
application-area: [all]
---
# Load only primary key fields for reference work
> Contributions welcome — open a PR to refine or extend this article.
## Description
Work that uses a record only for its identity — passing it to another procedure that will re-fetch what it needs, queueing a key for later processing, running existence checks, or building a reference collection — does not need non-key payload fields. `SetLoadFields` with only the primary key fields loads the minimum that preserves record identity while skipping everything else. On wide tables with large text, BLOB, or media fields the difference in memory and transfer is substantial.
## Best Practice
When the iterating code's body touches only primary key fields (or passes the record to another procedure that will apply its own `SetLoadFields`), declare `SetLoadFields` with just the primary key fields before applying filters and calling `FindSet`. Callers downstream that need more fields issue their own `Get` or extend the load explicitly.
See sample: `load-only-primary-key-fields-for-reference-work.good.al`.
## Anti Pattern
Using the default full-record load in loops whose body only reads the primary key, or forwards the record to another codeunit that immediately re-queries. The non-key payload is fetched across the wire and held in memory for the duration of the loop, then discarded unread.
See sample: `load-only-primary-key-fields-for-reference-work.bad.al`.