ebceff2332
These articles capture BC-specific mechanics agents still invert: partial-record JIT on writes, Reset clearing SetLoadFields, HttpClient inside write transactions, and batched number series, plus negative guidance that stops over-eager Query and IsEmpty "fixes". Co-authored-by: Cursor <cursoragent@cursor.com>
1.2 KiB
| bc-version | domain | keywords | technologies | countries | application-area | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
performance |
|
|
|
|
Do not call ChangeCompany inside a per-row loop
Contributions welcome — open a PR to refine or extend this article.
Description
ChangeCompany retargets a record variable to another company's data and drops the in-memory caches bound to the previous company. Calling it once per row in a multi-company scan therefore pays a cache reset on every iteration, even when consecutive rows share a company. Agents treat ChangeCompany like a filter. It is an isolation switch.
Best Practice
Group work by company. Call ChangeCompany once per distinct company, then FindSet/Get that company's rows. Reset the variable back when the batch finishes.
See sample: changecompany-in-loop-drops-caches.good.al.
Anti Pattern
repeat Rec.ChangeCompany(Buffer.Company); Rec.Get(Buffer."No."); until Buffer.Next() = 0 when Buffer is not ordered by company, or even when it is — if ChangeCompany still runs every row. The signal is ChangeCompany inside repeat/while keyed by a document line rather than by a company loop.
See sample: changecompany-in-loop-drops-caches.bad.al.