Business Central allows us to set or select the fields that will be initially loaded when the record is retrieved from its data source, improving the performance of objects such as OData pages and reports, and particularly beneficial when using table extensions in the application.
It was great to hear a lot of positive comments after I published my previous post so I hope I won’t disappoint you and that this post will be at least as useful as the previous one. At the moment, we are experiencing some performance issues because of the BLOB fields.
The partial records capability is one of the latest and more important feature available in Dynamics 365 Business Central for writing performant code. Using Record.SetLoadFields can help you on improving your performances, expecially when looping through records. In this way you can avoid joins with table extensions and you can load only the needed fields for your computation.