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.)
..
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.)
..