Continuing performance testing of queries on extended Business Central tables, today I want to look at the same dataset from a slightly different angle. If you read my previous post, you may remember the conclusion from the first test run: partial records are not a silver bullet to solve all performance problems in the application, but applying SetLoadFields on record variables can definitely help to protect the application from performance degradation in case when the application table is extended.
Tag Archives: Partial
Who benefits from partial records: The true magic of SetLoadFields
One of the key characteristics of the C/AL language and its more modern ancestor, AL, that makes it so attractive for developers, is simplicity that makes the journey into the application development world much more comfortable even for people coming from a different background.
Analyze (the lack of) Partial Records with Business Central Telemetry
I’ve been working with Business Central Telemetry a lot the last coulple of months, having to deal with deadlocks and such. And while doing so, quite some new ideas came to mind that I’d like to investigate by means of Telemetry.
Using partial records in Business Central (SetLoadFields)
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.
Partial Records: Interlude
This post was originally meant to be a “down and dirty” look in the platform’s engine room, exploring how Partial Records makes data fetching faster. But to satisfy the AL developers who are always asking for more examples, we will first have to take a quick detour in our series.
Partial Records: Interlude
This post was originally meant to be a “down and dirty” look in the platform’s engine room, exploring how Partial Records makes data fetching faster. But to satisfy the AL developers who are always asking for more examples, we will first have to take a quick detour in our series.
Partial Records: Part 1
Previously on this blog the Record type was presented and explored. In that post it was pointed out that the Record type and its accompanying API is large enough to warrant Directions sessions (and blog posts) for merely subsets of it. That was written with great confidence since I did so in our technical presentation on Partial Records at Directions.