Unplanned
Last Updated: 02 Jul 2024 14:25 by ADMIN

Steps to reproduce:

1. Add two lists at the same level:

2. Select list1 and click Ctrl+X

3. Select panel2 nested in list2 and press Ctrl+V:

4. Preview the report:

Unplanned
Last Updated: 04 Jul 2024 09:14 by insomnia

I am using the ObjectDataSource component and within my class, I use EF Core and initialize the DbContext with a connection string to pull data.

This works as expected in my application, however, when I try to use the assembly in the .NET Standalone Report Designer, it throws exceptions that one or more of the dependencies of the EF Core package cannot be loaded:

FileLoadException: Could not load file or assembly 'Microsoft.Extensions.Configuration
Unplanned
Last Updated: 28 Jun 2024 14:01 by ADMIN

Reports designed in Blazor Web Designer may have multiple shared data sources, only one of which can be used to bind details section data. That I understand.

A use of a secondary data source can be to provide data to which Report Parameters can be bound, such as providing dynamic localized values for any language and/or region. This I expect to do in every report of mine.

Right now, unless I've overlooked some existing mechanism, in each and every report for each field in such a secondary data source I have to manually create a new Report Parameter, bind it to the desired data source, and at least set the ValueMember to that data source field. This can be very time consuming, especially if there are a large number to be created.

It would seem possible for you to add a data source feature such that use of that data source in a report automatically does this for me for each selected field in the Select Query. That would save me a tremendous amount of design time!

Also, if you reply to this, perhaps you could tell me what constitutes a report's "Inline Data Source"? I have been unable to locate any discussion in your documentation nor any means to actually create one if that were useful to me.

Completed
Last Updated: 02 Oct 2025 09:18 by ADMIN
Release 2025 Q3

When I drag a data field from a DataSource component to the Report details section in the Standalone Report Designer, the Report > DataSource property is set automatically to the corresponding DataSource component.

In the Web Report Designer, when I drag a data field, the Report > DataSource property remains empty, and the Preview shows an empty report. It would be very helpful the same functionality to be introduced also in the Web Designer.

Unplanned
Last Updated: 12 Jun 2024 07:26 by Martin
Created by: Martin
Comments: 0
Category: Reporting
Type: Feature Request
2

I would like to have truly bitwise operators for my expressions. Here is my scenario.

I have a bitwise flag in my dataset which defines the status of a value. It can have up to 15 possible values set as true in one field. The issue is, that there doesn't appear to be any way that I can perform a check in my expression.

 I don't want to add 15 additional columns to my dataset that explicitly set these as true as that's total overkill.

The Logical/Bitwise operators article details that there are "bitwise" operators, but these are logic only. This forum post confirms this.

Completed
Last Updated: 14 Nov 2024 11:02 by ADMIN
Release 2024 Q4
Created by: Renu
Comments: 0
Category: Reporting
Type: Feature Request
1

The Uri user function can be selected from the functions list in the expression editor of the designer but when the report is previewed the following error message is shown.

The expression contains undefined function call Uri()

Unplanned
Last Updated: 06 Jun 2024 18:13 by Kim
Created by: Kim
Comments: 0
Category: Reporting
Type: Feature Request
2

Hi Team,

I would like to request that the rotate CSS attribute be added to the HtmlTextBox. 

Thank you!

Completed
Last Updated: 11 Feb 2025 15:24 by ADMIN
Release 2025 Q1

I export the same TRDP report that embeds a Bitmap image on Windows with GDI and on Linux Docker Container.

The result PDF file from the Linux environment is much bigger than the one generated on Windows.

Unplanned
Last Updated: 29 May 2024 12:49 by Markus

The following screenshot demonstrates what the ToC looks like when rendered with Skia on Linux.

Below is the expected result. Rendered with GDI on Windows.

Completed
Last Updated: 10 Jul 2024 10:00 by ADMIN
Release 2024 Q3

Since version 21.24.305 of the Native Angular Report Viewer, its DateTime parameter editors do not work if the user's machine does not use the en-US culture.

The following error message is displayed in the browser console when a DateTime parameter is present.

Error: The 'value' should be a valid JavaScript Date instance.
    at DateInput2.verifyValue (dateinput.js:1057:19)
    at DateInput2.writeValue (dateinput.js:1051:14)
    at DateInputComponent.ngOnChanges (progress-kendo-angular-dateinputs.mjs:10036:22)
    at DateInputComponent.rememberChangeHistoryAndInvokeOnChangesHook (core.mjs:4101:14)
    at callHookInternal (core.mjs:5136:14)
    at callHook (core.mjs:5167:9)
    at callHooks (core.mjs:5118:17)
    at executeCheckHooks (core.mjs:5049:5)
    at selectIndexInternal (core.mjs:11023:17)
    at ɵɵadvance (core.mjs:11012:5)

Completed
Last Updated: 07 Aug 2024 10:27 by ADMIN
Release 2024 Q3
Created by: Neel
Comments: 0
Category: Reporting
Type: Bug Report
2

Text boxes formatted with the 'en-US' culture and '{0:C}' format do not use the correct currency negative pattern in .NET Core.

For example, a field with a value of -2.55 should be formatted to '($2.55)' but instead it is shown as ' -$2.55'

 
Unplanned
Last Updated: 27 May 2024 08:22 by Nasja

When we add text with an Underlined font, it will be added as an extra embedded subset next to the same Normal/Bold font, which makes the files bigger.

This may be a major issue with large fonts such as Arial, as they get embedded twice in the PDF.

Completed
Last Updated: 07 Aug 2024 10:27 by ADMIN
Release 2024 Q3

The getReportParameters method of the HTML5 Report Viewer omits parameters with unset values that have their AllowNull property set to False.

The reportSource method of the HTML5 Report Viewer can be used as an alternative.

Completed
Last Updated: 07 Aug 2024 10:27 by ADMIN
Release 2024 Q3
Created by: Lars Rikard
Comments: 0
Category: Reporting
Type: Feature Request
1

The WPF Report Viewer should support rounded corners.

Currently, I am not allowed to do the following:

<telerikReport:ReportViewer Grid.Row="1"
                            Grid.Column="1" 
                            Name="reportViewer1"
                            ReportSource="{Binding ReportSource}">
    <telerikReport:ReportViewer.Resources>
        <Style TargetType="telerikReport:ReportViewer" BasedOn="{StaticResource {x:Type telerikReport:ReportViewer}}">
            <Setter Property="BorderBrush" Value="{telerik:Windows11Resource ResourceKey=PrimaryBorderBrush}"/>
            <Setter Property="BorderThickness" Value="1"/>
            <Setter Property="Margin" Value="5"/>
            <Setter Property="CornerRadius" Value="4"/>
        </Style>
    </telerikReport:ReportViewer.Resources>
</telerikReport:ReportViewer>

Completed
Last Updated: 16 May 2024 08:28 by ADMIN
Release 2024 Q2

Clicking on the Value property of a Report Parameter from the Report Explorer in the .NET Standalone Report Designer throws the following error:

The issue is not present in the Standalone Report Designer for .NET Framework.

Completed
Last Updated: 23 May 2025 08:03 by ADMIN
Release 2025 Q2
When exporting a report using the ReportProcessor class, the properties defined in the RuntimeSettings property of the report are disregarded by the Reporting engine.
Need More Info
Last Updated: 14 May 2024 08:48 by ADMIN
Created by: Simon
Comments: 2
Category: Reporting
Type: Feature Request
2

Good afternoon,

As per support ticket 1650746, could I please request that Telerik reporting could one day work with minimal APIs as opposed to controllers?

There is also the dependency on Newtonsoft for the JSON side of things. Up until trying to implement reporting, I had removed the Newtonsoft nuget package and was trying to use System.Text instead throughout my project. Perhaps in time, it could be a bit more agnostic when it comes to the provider.

Many thanks,

Rawden.

Completed
Last Updated: 07 Aug 2024 10:27 by ADMIN
Release 2024 Q3

When a report contains multiple DateTime parameters, the viewer assigns the first value to all of them regardless of their default values or the values passed in the viewer's report source.

Additionally, if one clicks the preview button quickly after changing the value of a DateTime parameter, the old value is passed to the service even though the parameter editor is updated. To avoid this, the user needs to wait a second before previewing.

  
Unplanned
Last Updated: 02 May 2024 08:25 by Steve

When testing integer values outside the range of System.Int32 (-2147483648 to 2147483647) for a multi-value integer parameter, I started to get the error:

An error has occurred while processing Report '___':
Cannot perform '=' operation on System.Int32 and System.Int64.

I narrowed this down to the "In" and "Between" operators. For example, the expression evaluating a literal integer value against the multi-value parameter:

= 0 In Parameters.IntegerMultiVal.Value

It appears that the literal integer is being converted, internally, to Int32 and compared against the contents of the multi-value parameter as Int64 - though the error only occurs when a value outside the Int32 range is present.

Direct comparison to a single parameter value outside the Int32 range appears to work fine:
= Parameters.IntegerSingleVal.Value = 0
Additionally, when replacing the literal integer in the expression with a single value parameter set to the same value, it evaluates without error:

= Parameters.ZeroVal.Value In Parameters.IntegerMultiVal.Value

This was tested and reproduced in the HTML5 report viewer and the standalone report editor.

Unplanned
Last Updated: 30 Apr 2024 10:58 by Salvador

The HTML5-based report viewers use the following navigation icons.

  • Arrow with a line to navigate to the next/previous page.
  • Double arrows to navigate to the first/last page.

This is unintuitive and inconsistent with the desktop and native report viewers.
The navigation icons should instead be:

  • Single arrow to navigate to the next/previous page.
  • Arrow with a line to navigate to the first/last page.