Hello Telerik Reporting Community,

We have released a new version of Telerik Reporting today, 2024 Q1 (18.0.24.130). Please update your existing installation at your earliest convenience.

You can review the Legacy Installer Vulnerability - Telerik Reporting article to learn more details about why we are recommending customers to update.

To get the new version, take the following steps:

1. Go to Downloads | Your Account. 
2. Select Telerik Reporting.
3. Download the msi installer file, run it, and follow the steps to completion.

Notes

As the KB article explains, the issue pertained only to the old installer component, and not Telerik Reporting contained within the installation package. It does not affect any applications you’re using Telerik Reporting with.

If you have a rare situation where you cannot update the PC installed version, there are various ways to keep a project using an older version of reporting even though the PC has a newer version installed.

• NuGet Option: Update your projects to use the Telerik Reporting NuGet packages, instead of local DLLs (see https://docs.telerik.com/reporting/getting-started/installation/installation-approaches#using-nuget-packages).

• Copied Assemblies Option: Copy the older version’s DLLs to the project directory, then update the project references to use the copied assemblies (instead of the assemblies in C:/Program files (x86)/Progress/Telerik Reporting [older version]/)

We highly recommend you open a Technical Support Ticket if you have a complex situation and would like to ask questions before updating the PC’s installed version. You can open a Support Ticket here => https://prgress.co/DevToolsSupport.

hi,

    I would like to ask, why does Telerik Report request the /info api multiple times? Can this info interface be requested in other ways to reduce the number of times?

thanks.

I have base configuration in appsettings.json (.Net 9 application)

    "telerikReporting": {
        "assemblyReferences": [
            {
                "name": "My.Assembly.Reports"
            }
        ],
        "extensions": [
            {
                "name": "PDF",
                "parameters": [
                    {
                        "name": "FontEmbedding",
                        "value": "Subset"
                    }
                ]
            }
        ]
    }

It works. But now I have multi layered configurations. There is appsettings.json and multiple other configuration files as customer1.json, customer2.json etc. Every customer has own settings and ovn assemly with reports. All is registered in program.cs in standard way. And it does not work. Seems that reportings have some hardcoded logic to read only from file named appsettings.json and whole configuration system of .Net is ignored.

It ends with errors:

An error has occurred while processing Report 'XXX':
 The type "XXX.TelerikReport.ObjectDataSources.XXX.Root" contained in assembly 
"XXX.TelerikReport.ObjectDataSources, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" cannot be loaded. 
To help improve the application's security, the reporting engine prevents loading types that are not essentially needed or listed as trusted by the user. If you 
consider particular types or assemblies as trusted include them in the corresponding TypeReferences or AssemblyReferences element of the 
'Telerik.Reporting' configuration section in the application's configuration file

Am I right? How can I split configs to multiple settings files? Can reporting work with configuration system as designed in .Net?

Our .NET 8 project references .NET Standard Telerik.Reporting.dll.

After upgrading to Telerik Reporting 19.0 we get compiler warnings because of conflicting references.

Apparently, Telerik.Reporting.dll references .NET 9 DLLs (for example "System.Text.Json 9.0.0") while our .NET 8 project obviously references .NET 8 DLLs ("System.Text.Json 8.0.0").

I'm surprised this is happening because I thought Telerik.Reporting as a .NET Standard DLL should be independent of these .NET versions?

Do we have to go back to Telerik Reporting 18 to avoid these conflicts?

We are on .NET 8 because it has LTS (long term support) by Microsoft.

Hi all,

I'm developing a report and I don't know how to layout it.

The data source is a JSON DataSource and his structure is the following :

public class School
{
	public string Name { get; set; }
	public List<Class> Classes { get; set; }
}

public class Class
{
	public string Name { get; set; }
	public List<Student> Students { get; set; }
	public List<Teacher> Teachers { get; set; }
}

public class Student
{
	public string FirstName { get; set; }
	public string LastName { get; set; }
}

public class Teacher
{
	public string FirstName { get; set; }
	public string LastName { get; set; }
	public string Role { get; set; }
}

The desired layout is illustrated on the join file DesiredLayout.png and the report definition is joined too (containing datasource).

As you can see in the report definition, I don't use Header section. Because my list of teachers, on the top right, cannot be in a Header section.

And my problem is when the list of students for one class take more than one page, the school name, the class name and the list of teachers don't repeat.

My second problem is for the numbering on the footer. I don't know how to make it correctly.

Hi,

Can I ask does the older version of Telerik Report (Reporting 2017) supports visual studio 2019 ?

If it does, is it possible to provide instruction on how to enable it please?

It seems to work for visual studio 2017, but menu will not show on visual studio 2019.

Many thanks

Regards

So, I've spent about a week trying to resolve an issue where we had one sneaky user function annotated with [Function] that worked fine before the change, but when we updated to 19.0.25.211 everything stopped working normally which is documented but I would say this is really a change that users should be made more aware of.

https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-2025-q1-19-0-25-211

We constantly evaluate the release history paying special attention to "breaking changes" but this is under the category of "improved" and no real indication that it could negatively affect someone's pre-existing reporting should they use [Function] in a way that is now .. changed. Especially when that change causes reporting errors, that are perceived as "broken".

We're already having a hard time justifying the very very fragile nature of using Telerik Reporting (re: vs designer, core vs netframework, the ticket was created in 2018 ...... !!!! Did you know your competitor's vs designer works properly in netcore/netframework??) but this was just so painful. Adding something more to the release notes would have prevented so much wasted time.

Hi,

Iam exporting date column values e.g. 23/11/2023 using Telerik to an .xlsx excel file.

From exported excel, if you right click the value -> Choose Format cell, it is showing as General

How can this be shown as Date.  What changes to make in Telerik file before exporting.