microsoft / microsoft/alguidelines
AL Performance Guidelines Summary
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 208
- Forks
- 79
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 2
Description
Rule 2: Use SetLoadFields for Optimal Data Retrieval
Agree with the rule but the examples aren't that good
// Bad example (avoid SetLoadFields after filtering)
Item.SetLoadFields("Item Category Code");
Item.SetRange("Third Party Item Exists", false);
Item.FindFirst();
the order of the two first line should not be important as the loadfield and the strange should "kick in" before the findfirst
Rule 3: Use Temporary Tables, Dictionaries, and Lists for Performance
Use only temptable for minor dataset! and newer with a write back
Rule 5: Performance Impact Analysis
This a hard one
in general we should not use count instead we should assume that Item, Customer .. (Masterdata) contains large datasets (same for history table.)
..
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the AL Performance Guidelines sections for Rules 2, 3, and 5. Compare the current examples and recommendations with the concerns raised in this issue, then define the revised guidance and examples; done means those sections clearly address ordering, temporary data structures, write-back, and large datasets.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, performance
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100