We work in a project with more than 100 parameters. The parameters are sorted in the order we added them.

It is hard to look for a parameter when we need to do a change. A right click "sort" would be great.

When the latest Kendo UI version is used, the ellipsis in the Web Report Designer's Report Explorer tree are invisible, and the context menus of some report items cannot be opened.

For example, adding shared data sources to a report is not possible because this functionality is accessible through the context menu of the [Shared Data Sources] collection in the explorer tree.

Expected behavior:

Actual behavior:

To work around the issue, use the 2022.3.913 Kendo UI version on the Web Report Designer page.

When I enable accessibility in the Angular Report Viewer, based on the HTML5 Report Viewer, I get the following console error:

Uncaught TypeError: Cannot read properties of undefined (reading '_controller')
at telerikReportViewer:1:15863
at Ce. (telerikReportViewer:1:16167)
at Ce.n (telerikReportViewer:1:26372)
at Ce.trigger (telerikReportViewer:1:26686)
at ce (telerikReportViewer:1:32782)
at Object.updateUI (telerikReportViewer:1:43789)
at telerikReportViewer:1:93236

The report viewer continues being functional despite the error but accessibility text is missing for page number, export, and buttons(incl. parameters area).

Hello,

I am working on Blazor reporting project and I have described the situation already in this post:

https://www.telerik.com/forums/report-viewer-and-web-designer-in-blazor#zGr6FO2mDEmkfLWIP_T_9A

Please add Blazor ReportDesigner wrapping Your HTML designer and use .NET 5 js/css isolation to manage js/css loading by the component itself and not globally.

Thank You

Marek Ištvánek

Hi Team,

When using the WPF ReportViewer, Reporting appears to only fetch settings from appsetting.json, and ignores any other values coming from things like secrets.json, or any other configuration builder.

Please see the following forum thread, where Lance replied with a test that verifies none of the values from secrets.json were accessible to Reporting even though they are in the global Configuration (at 13 Sep 2024, 12:34 PM (ET) => https://www.telerik.com/forums/simple-wpf-reportviewer-example). Reporting only respected appsettings.json.

Proposed Solution

settings.AddTelerikReporting(configuration);

That allows me to pass the full view of the Configuration to Reporting that allows it to see more than what might only might be in appsettings.json (secrets, imported configurations, etc).

Thank you,

Brad

Telerik,

This is a feature request to add the ability to override a connection itself and not just the connection string.

The motivation behind this is for IAM based authentication, where usernames and passwords are no longer used but usernames and short lived tokens are.

Many database providers provide a Factory or Builder to allow a Connect to be built that allows the password to be requested when needed. In the case of Postgres, this is the NpgsqlDataSourceBuilder class.

I'm not sure what the contract would look like to achieve this, but setting the connection itself, one way, shape, or form, is greatly needed.

Thanks,

Shawn

Currently If you want to hide one filter out of many based on other value. this is feature is not available in report now. below the my ticket for you same. I wish this feature include out of the box.

https://www.telerik.com/account/support-tickets/view-ticket?threadid=1102630

Telerik.Reporting.nupkg has a dependency on ResXResourceReader.NetStandard.

Our 3rd party security audit has found the missing Digital Signature of this DLL. A digital signature would aid in verifying its authenticity and integrity.

The labels of the Send Mail form in the HTML5 Report Viewer and its wrappers do not conform to accessibility standards. They refer to form fields using the field's name attribute instead of the id attribute.

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.

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>

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.

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'

When the parametersAreaVisible property of the report viewer is set to true, the parameters area of the viewer should be open by default if a report that has visible parameters is being previewed.

However, when a mobile device is used, the parameters area is closed by default.

Additionally, the arrow used to open the parameters area is hidden by default. The device orientation needs to be toggled to horizontal and back for the arrow to appear.

I use cascading parameters and need to specify their Text property with an Expression, as the label should be translated through a User Function. My parameters shouldn't have values initially.

The problem is that the dependent parameter's Text Expression is not evaluated when the report is first displayed by the designer or viewer. The label shows the Expression instead.

If I make the independent parameter Nullable, the issue doesn't occur, but I prefer not to allow Null values.

The problem is shown in the linked muted video.