New to Telerik Report Server? Download free 30-day trial

How to configure Telerik Report Server to use reports with custom functions

Environment

Product Progress® Telerik® Report Server

Description

Extending the report engine of the Report Server is not supported out of the box. It requires some manual steps.

Solution

  1. Copy the assembly containing the user function(s) in:

    • The bin folder of the Report Server web application, i.e. [Telerik Report Server installation folder]\Telerik.ReportServer.Web\bin (usually C:\Program Files (x86)\Progress\Telerik Report Server\Telerik.ReportServer.Web\bin)
    • for scheduling services only - in the folder of the scheduling service, i.e. [Telerik Report Server installation folder]\Services (usually C:\Program Files (x86)\Progress\Telerik Report Server\Services)
  2. Register the same assembly in the corresponding application configuration files, using the snippets that could be found in the article Telerik Reporting assemblyReferences Element.

    • for Report Server web application:

      1. in versions up to R3 2018 SP2 (4.2.18.1129) in [Telerik Report Server installation folder]\Telerik.ReportServer.Web\Web.config (usually C:\Program Files (x86)\Progress\Telerik Report Server\Telerik.ReportServer.Web\Web.config)
      2. from version R1 2019 (5.0.19.116) in [Telerik Report Server installation folder]\Telerik.ReportServer.Web\TelerikReporting.config (usually C:\Program Files (x86)\Progress\Telerik Report Server\Telerik.ReportServer.Web\TelerikReporting.config)
    • for scheduling services only:

      1. in versions up to R3 2018 SP2 (4.2.18.1129) in [Telerik Report Server installation folder]\Services\Telerik.ReportServer.ServiceAgent.exe.config (usually C:\Program Files (x86)\Progress\Telerik Report Server\Services\Telerik.ReportServer.ServiceAgent.exe.config)
      2. from version R1 2019 (5.0.19.116) in [Telerik Report Server installation folder]\Services\TelerikReporting.config (usually C:\Program Files (x86)\Progress\Telerik Report Server\Services\TelerikReporting.config)
  3. (optional) If the custom functions are aggregate functions, it would be necessary for the Telerik Reporting version used for creating the custom assembly, and the one used in the Telerik Report Server to match.

  4. (optional) If the Telerik Reporting version on the Report Server is different, add a binding redirect to point to the version of Telerik Reporting used to create the custom function in the same way as explained in the article Standalone Report Designer Configuration File.
In this article