(RDLC) Reporting performance on sandboxes

  • Article

Important

This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.

Note

These release notes describe functionality that may not have been released yet. To see when this functionality is planned to release, please review What's new and planned for Dynamics 365 Business Central. Delivery timelines and projected functionality may change or may not ship (see Microsoft policy).

Before we shipped Dynamics NAV 2013 R2, we discovered a huge performance regression in the runtime for RDLC reports. This was because we upgraded to .NET version 4.0, and we needed to set the .NET runtime to use legacy code access security policy to make RDLC reports work with no performance degradation. Fast forward five years, when we enabled debugging in Business Central sandboxes. This required us to disable code access security on sandbox clusters. Unfortunately, this introduced the old regression on RDLC report performance. In the Business Central April 2019 release, we got rid of the performance problem by running RDLC reports fully in a different .NET AppDomain.

Solved memory leak in RDLC reporting

The old implementation of RDLC in the Business Central server had a small memory leak with report executions. In the Business Central April '19 release, we no longer have this memory leak, because we regularly recycle the .NET AppDomain that is used for reporting.

Tell us what you think

Help us improve Dynamics 365 Business Central by discussing ideas, providing suggestions, and giving feedback. Use the Business Central forum at https://aka.ms/businesscentralideas.