#130 knowledge(performance): align SetLoadFields placement with AL Guidelines

Pull request · merged into main on 2026-09-02 by JesperSchulz · 7 files (+11 -9), 7 AL · other · tier official · reviewed (checked by Opus)

What changed

• Reordered SetLoadFields to appear after SetRange/SetFilter in six AL code samples to match AL Guidelines convention
• Documented that the order does not affect query projection, as filtered fields are always loaded regardless
• Added explicit guidance that readability placement is not a performance defect to prevent false-positive review warnings
• Updated documentation to clarify the distinction between readability and behavioral requirements

AL objects touched

• microsoft/knowledge/performance/avoid-cloning-records-before-modify-delete-in-loops.bad.al: modified, not in the BC? snapshot
• microsoft/knowledge/performance/avoid-cloning-records-before-modify-delete-in-loops.good.al: modified, not in the BC? snapshot
• microsoft/knowledge/performance/load-only-primary-key-fields-for-reference-work.good.al: modified, not in the BC? snapshot
• microsoft/knowledge/performance/use-setautocalcfields-for-per-row-flowfields.bad.al: modified, not in the BC? snapshot
• microsoft/knowledge/performance/use-setautocalcfields-for-per-row-flowfields.good.al: modified, not in the BC? snapshot
• microsoft/knowledge/performance/use-setloadfields-for-partial-records.good.al: modified, not in the BC? snapshot
• microsoft/knowledge/performance/use-setloadfields-for-partial-records.md: modified, not in the BC? snapshot

Context

• Fixes: #120 Clarify the correct order of Filtering and SetLoadFields (closed)
• Systems: development
• From the description: “The order is a readability convention, not a behavioural one.”

Source: metadata of a merged pull request in microsoft/BCQuality (bcquality): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).