Recommend using <Set|Add>LoadFields

[fvet]

As we now and then have to troubleshoot issues with incorrect usage of SetLoadFields, it would be great to revise some of the ideas listed here StefanMaron/BusinessCentral.LinterCop#218

Specific case we encountered

// Pseudo code
local procedure()
var
   Item: record Item;
begin
  Item.SetLoadFields(xxx);  // << Should not be used in relation with Modify, Delete
  Item.Get(ItemNo);
  ....
  Item.Modify();
end;

[Arthurvdv]

Thanks for raising the idea! I’ve created a new rule for this in PlatformCop: Do not use partial records before write operations (PC0031).

It is now available in the alpha release v0.7.1-alpha.1.
You can easily switch channels in the VS Code extension to jump over to the alpha channel to install this version.

It would be great if you could try it out and share some feedback on the new rule and its behavior. For now, it’s limited to local variables, similar to the PC0030 rule. In the future, we may expand it to include global variables and/or parameters but for now I left this out-of-scope as it would increase the complexity of the rule significantly.

[Arthurvdv]

With the release of v0.8.0 the new rule is now general available. @fvet thanks again for (re)creating the idea here!