From 6b3d740bbbced8d9ac79f50abe76b73ceb13a31a Mon Sep 17 00:00:00 2001 From: Luuk Date: Thu, 10 Aug 2023 10:38:28 +0200 Subject: [PATCH] #SetLoadFields --- content/docs/BestPractices/SetLoadFields/Index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/docs/BestPractices/SetLoadFields/Index.md b/content/docs/BestPractices/SetLoadFields/Index.md index 11453790..465aea6f 100644 --- a/content/docs/BestPractices/SetLoadFields/Index.md +++ b/content/docs/BestPractices/SetLoadFields/Index.md @@ -8,7 +8,7 @@ See the documentation on learn.microsoft.com for more information about [SetLoad For the performance of your code it is important that you use SetLoadFields as much as possible. -If you want to retrieve a record from the database to check if the record is available the advice is to use SetLoadFields on the primary key fields of the table so only those fields will be retrieved from the database. +If you want to retrieve a record from the database to check if the record is available always use SetLoadFields on the primary key fields of the table so only those fields will be retrieved from the database. ## Bad code @@ -26,20 +26,20 @@ if not Item.Get(ItemNo) then ``` -Place the SetLoadFields in the code before filtering the record (there is no need to record filter fields in the SetLoadFields because these will be retrieved automatically). +Place the SetLoadFields in the code before the line of the Get (or find). (there is no need to record filter fields in the SetLoadFields because these will be retrieved automatically). ## Bad code ```AL -Item.SetRange("Third Party Item Exists", false); Item.SetLoadFields("Item Category Code"); +Item.SetRange("Third Party Item Exists", false); Item.Get(ItemNo); ``` ## Good code ```AL -Item.SetLoadFields("Item Category Code"); Item.SetRange("Third Party Item Exists", false); +Item.SetLoadFields("Item Category Code"); Item.Get(ItemNo); ```