Performance recommendations
When you create a report, there are always two phases, the construction of the dataset and the creation of the layout. I will provide some recommendations for the report development process with performance in mind.
Although you can probably achieve your goal without following these guidelines, you will notice that, after a while, when the database grows and more users run the system, things get slower. That is why it is important to always have performance at the forefront. The idea is to prevent problems occurring, instead of having to solve them when they eventually do.
The dataset
When you create your dataset, you can make changes without major consequences. If your report has a layout already then modifying the dataset will have a big impact and, as a result, you will probably also need to spend some time updating the layout accordingly.
There are a couple of techniques you will need to use:
- Optimize the C/AL code for the report. For example, use
currreport...
