---
id: change/bcquality/130
type: change
title: "#130 knowledge(performance): align SetLoadFields placement with AL Guidelines"
summary: BCQuality aligned SetLoadFields code examples with AL Guidelines by placing filters before SetLoadFields, clarifying that this order is a readability convention rather than a performance requirement.
tier: official
language: en
tags:
  - other
  - main
system: development
review:
  state: reviewed
  by: opus
  at: "2026-10-08T02:06:43.037Z"
  flags: []
generated:
  at: "2026-10-08T01:26:53.141Z"
  pipeline: 0.2.0
  prompts:
    extract-change: 1
  input_hash: 3e848d1ec2a25a36249015673911827cfefd036f
evidence:
  - kind: code
    url: https://github.com/microsoft/BCQuality/pull/130
    title: "microsoft/BCQuality#130: knowledge(performance): align SetLoadFields placement with AL Guidelines"
    date: "2026-09-02"
    commit: 3e848d1ec2a25a36249015673911827cfefd036f
    t: null
    quote: The order is a readability convention, not a behavioural one.
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
  changes: []
number: 130
repo: microsoft/BCQuality
source_id: bcquality-prs
url: https://github.com/microsoft/BCQuality/pull/130
kind: pr
base_branch: main
major: null
merged_at: "2026-09-02T12:44:09Z"
author: JesperSchulz
author_type: User
community_contribution: false
labels: []
change_class: code
change_kind: other
behavior_change: false
breaking: false
files:
  count: 7
  additions: 11
  deletions: 9
  al: 7
apps: []
objects_touched: []
objects_unjoined:
  - path: microsoft/knowledge/performance/avoid-cloning-records-before-modify-delete-in-loops.bad.al
    status: modified
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/avoid-cloning-records-before-modify-delete-in-loops.good.al
    status: modified
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/load-only-primary-key-fields-for-reference-work.good.al
    status: modified
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/use-setautocalcfields-for-per-row-flowfields.bad.al
    status: modified
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/use-setautocalcfields-for-per-row-flowfields.good.al
    status: modified
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/use-setloadfields-for-partial-records.good.al
    status: modified
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/use-setloadfields-for-partial-records.md
    status: modified
    reason: not-in-snapshot
obsoletions: []
backports: []
fixes_issues:
  - 120
work_items: []
systems:
  - development
quote: The order is a readability convention, not a behavioural one.
joined_against:
  major: null
  commit: null
---

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

> BCQuality aligned SetLoadFields code examples with AL Guidelines by placing filters before SetLoadFields, clarifying that this order is a readability convention rather than a performance requirement.

[Pull request](https://github.com/microsoft/BCQuality/pull/130) · 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](https://github.com/microsoft/BCQuality/issues/120) (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).