Use AddLoadFields on OnOpenPage and OnPreDataItemTrigger

[lv-janpieter]

Just dropping a thought, and i'm curious what the community thinks of this.

In API pages and reports utilize partial record loading to optimize performance by loading only specified fields. Microsoft recommends using the AddLoadFields method in the OnOpenPage trigger for pages and the OnPreDataItem trigger for reports to explicitly load additional fields referenced in AL code but not included in the page or report dataset. This rule proposes a code analyzer check to identify fields used in AL code (e.g., in triggers, functions, or calculations) that are not explicitly loaded via AddLoadFields. If such a field is detected, the analyzer will issue a warning to alert developers of potential runtime errors or performance issues due to missing field data. The rule will apply to API pages, reports (and maybe other objects in the future).

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-partial-records

Benefits:

• Improved performance by reducing JIT calls
• reduce inconsistent reads and JIT load errors

Implementation:

• Scan all fields used in dataset / page layout
• Scan all loaded fields with AddLoadFields in OnOpenPage / OnPreDataItem
• Scan all fields used in code
• Issue warning for all fields in code that do not exist in dataset/ page layout and have not been added with AddLoadFields

Considerations:

• ignore primairy key fields
• ignore temporary records