Completed
Last Updated: 20 Jan 2023 16:33 by ADMIN
Release R1 2023
Created by: Neli
Comments: 3
Type: Feature Request
14
Please, make possible setting the report viewer options in the initialization of the Web Report Designer. For example, pageMode, viewMode and so on.
Completed
Last Updated: 20 Jan 2023 12:34 by ADMIN
Release R1 2023

I have encountered scenarios where I want to return different results based on fields value or some expression. While I can use nested ternary operations this is not ideal as it can be difficult to read and maintain, particular for newer report designers. It would be helpful to have SWITCH and IFS statements modeled after those provided by Excel.

SWITCH would be helpful for cases where I want to check against a few different literal values and return different results.

IFS would be helpful for cases where I want to evaluate different expressions and return different results.

Modeling these after those in Excel would be sufficient, though, for more advanced cases being able to write C# code inline with the report would be helpful (will submit as a separate request).

Completed
Last Updated: 19 Jan 2023 08:31 by ADMIN
Release R1 2023
I have a report that has a sub-report inside it and it's working just fine.

The sub-report can give one or multiple lines as output for a single row in the master report.
However, when a row's height in the master report is too high (due to the output of other cells, not the sub-report), then the sub-report's output doesn't fill the gap in the master report even when I use anchoring to top and bottom.
Completed
Last Updated: 18 Jan 2023 11:55 by ADMIN
Release R1 2023

in the new/current Version "16.2.22.914", when dragging an DataSource-Field on the Report, the resolved expression is wrong.

In the previous Version "16.2.22.622", this worked as expected, see Screenshot.

 

The attached report demonstrates the issue.

Completed
Last Updated: 18 Jan 2023 11:55 by ADMIN
Release R1 2023

I have posted a video that shows the issue.  If I use the string builder for a textbox value and select a nested property, such as DayOfWeek, for a date, then it adds:

=Fields.DayOfWeek

which fails on Preview and is wrong.  Instead it should add:

=Fields.Birthday.DayOfWeek

 

Please fix this.  I know that I can go type ".Birthday" to fix the issue, but it really should add the nested properties properly.

Completed
Last Updated: 18 Jan 2023 11:55 by ADMIN
Release R1 2023

Using the Npgsql data provider of version 6.0.7 leads to the following error when there is a DateTime SQL parameter:

Can't write CLR type System.String with handler type TimestampTzHandler or Can't write CLR type System.String with handler type TimestampHandler.

This error is thrown only on Design-Time because the Design-Time value for the SQL parameter does not respect its selected DbType and is instead always a string.

Completed
Last Updated: 10 Nov 2022 17:27 by ADMIN
Release R3 2022 SP1
My report has 4 levels of nested subreports. Each child subreport receives its data from the parent with Binding to a data field from the parent report data source. This works correctly with versions 11.2.17.913 and 13.2.19.1030 but doesn't show the correct data with version 15.0.21.326. For details see the forum post Invalid subreport data when updating to latest telerik reporting version.
Completed
Last Updated: 09 Nov 2022 14:00 by ADMIN
Release R3 2022 SP1
1. Start HTML5 or Blazor viewer or designer in a .NET7 RC1 application

Expected: Report Catalog report shown.
Actual: Error creating report instance (Report = 'Report Catalog.trdp'). An error has occurred. A possible object cycle was detected. This can either be due to a cycle or if the object depth is larger than the maximum allowed depth of 64. Consider using ReferenceHandler.Preserve on JsonSerializerOptions to support cycles. Path: $.
Completed
Last Updated: 09 Nov 2022 13:31 by ADMIN
Release R3 2022 SP1
Created by: Stephen McDaniel
Comments: 1
Type: Bug Report
1

Currently a single instance of the WPF Report Viewer will often use multiple different HttpClient instances to talk to the Report Server.  This means that cookies added as part of earlier requests may not be sent in later requests.  If the Report Server is behind a load balancer that uses cookies to implement 'sticky sessions', this loose behavior with cookies will cause requests to get routed to different servers which is not ideal.  It is possible to use a storage mechanism on the server that natively supports a web farm (such as the Redis storage option) but that can be tricky to set up.  

Instead, if the report viewer were to re-use the same HttpClient instance for all requests (including initial render request, export requests, print requests, etc.), the load balancer could work to route all requests to the same web server and then any storage mechanism (such as the simple File storage option) would work.

This issue was reported back in 2017 and I'm running into the problem again in 2022.  See: https://www.telerik.com/forums/wpf-reportviewer-cookie-behavior

Completed
Last Updated: 09 Nov 2022 13:31 by ADMIN
Release R3 2022 SP1

Due to breaking changes related to the Kendo state classes - https://docs.telerik.com/aspnet-core/styles-and-layout/components-rendering-overview#state-classes, report parameters loaded in the HTML5 Report Viewers that use the ListView widget, are not selected properly, thus the report is not updated with a new report source and the data does not change.

 
Completed
Last Updated: 09 Nov 2022 13:31 by ADMIN
Release R3 2022 SP1

Using the Default or Material Kendo Theme (v5.6.0) with the Telerik HTML5 Report Viewer, the Boolean parameter which uses a Checkbox for it's display, is not visible (this may affect other themes as well).

I confirmed an older version v4.40.0 has a height and width set for the k-checkbox CSS class as such:

https://unpkg.com/@progress/kendo-theme-material@4.40.0/dist/all.css

.k-checkbox {
    border-radius: 2px;
    margin: 0;
    padding: 0;
    width: 16px;
    height: 16px;
    line-height: initial;
    border-width: 2px;
    border-style: solid;
    outline: 0;
    box-sizing: border-box;
    background-position: center;
    background-repeat: no-repeat;
    background-size: contain;
    display: inline-block;
    vertical-align: middle;
    position: relative;
    cursor: pointer;
    -webkit-appearance: none;
}

while the latest v5.6.0 does not:

https://unpkg.com/@progress/kendo-theme-material@5.6.0/dist/all.css

.k-checkbox {
    margin: 0;
    padding: 0;
    line-height: initial;
    border-width: 2px;
    border-style: solid;
    outline: 0;
    background-position: center;
    background-repeat: no-repeat;
    background-size: contain;
    display: inline-block;
    flex: none;
    vertical-align: middle;
    position: relative;
    cursor: pointer;
    -webkit-appearance: none;
}

The checkbox is actually on the page, but is so small it's basically invisible and completely unusable, requiring a manual CSS override to fix.

Completed
Last Updated: 09 Nov 2022 13:31 by ADMIN
Release R3 2022 SP1

Boolean parameter checkbox is with a small size in the HTML Viewer with Kendo SASS theme created with ThemeBuilder.

The current workaround is to use the following CSS to set the width and height of the checkbox:

.k-checkbox{
   width: 16px !important;
   height: 16px !important;
}

 

Completed
Last Updated: 09 Nov 2022 13:31 by ADMIN
Release R3 2022 SP1
The same report is rendered twice in two different threads. It would happen randomly because it relies on two threads both trying to modify that dictionary in the same instant. 
Completed
Last Updated: 09 Nov 2022 13:30 by ADMIN
Release R3 2022 SP1

In the Web Designer, I can create OhlcSeries but I cannot find a way to provide the OHLC marks. Whatever I enter for Y value, in the Design view I see the error "The XML serializer cannot resolve type with name: Telerik.Reporting.OhlcMarks". In Preview the error is "An error has occurred while processing Graph 'graph1':ohlcSeries1: OHLC values value cannot be null or empty when using NumericalScale".
If I created an OHLC chart with the Standalone Designer and opened it in the Web Designer, the Y value would display "[object Object]" as seen in the linked screenshot.

Completed
Last Updated: 09 Nov 2022 13:30 by ADMIN
Release R3 2022 SP1
There is a behavioral difference between .NET Framework and .NET assembly loading, which results in inconsistent behavior in the .NET EUD. Currently, referenced assemblies can only be loaded by file name. (i.e. MyAssembly should be passed as MyAssembly.dll in the config). The former behavior (loading by name) should be enabled for better consistency.
Completed
Last Updated: 04 Oct 2022 15:07 by ADMIN
I have prepared and localized a report successfully in the Standalone Designer. When I opened and modified it in the Web Designer, it lost all localization information. The Localized property was also reset to False.
Completed
Last Updated: 21 Sep 2022 06:19 by ADMIN

New development is being done with net core 3.1 and netstandard 2.1 and we can no longer create reports in the Report Designer using the ObjectDataSource.

Seems like it's time to update the standalone Report Designer for these new standards.

Completed
Last Updated: 19 Sep 2022 09:42 by ADMIN
Created by: Franz
Comments: 8
Type: Feature Request
12

Problem description:
On ".net Framework" it is a supported scenario that assemblies with datasources and/or functions are loaded into the standalone ReportDesigner. This assemblies are used while designing and later also in the ReportViewer while executing the report. Feature described here https://docs.telerik.com/reporting/standalone-report-designer-extending-configuration

Now that .net 6 is release by MS the same feature is needed there. The problem is that the "standalone ReportDesigner" is targeting ."net framework" which means it can only load assemblies targeting ".net framework" or up to ".net standard 2.0". But that is not sufficient because on ".net standard 2.0" only EntityFrameworkCore3.1 is supported and all newer version (EF Core 6.0) are not.  See here https://docs.telerik.com/reporting/knowledge-base/use-reporting-in-dotnetcore-with-entity-framework-core

So in summary:
It`s not possible to use EF Core 6.0 (and upwards) DataSources in the given "standalone ReportDesigner" because it is targeting .net framework. It`s critical to be able to use the newest EF Core versions as DataSource to not be blocked from upgrading a ".net framework" application to .net 6 where the described feature/scenario is used. I need to use the "standalone ReportDesigner" because it gets shipped with the application to edit the reports individually by the enduser. The "VS ReportDesinger" is going to get the upgrade but this would only be usable as a developer before shipping the application.

Feature request:
Upgrade the "standalone ReportDesigner" to target .net 6.

Completed
Last Updated: 14 Sep 2022 14:34 by James
Release R3 2022

Steps to reproduce the problem:

1. Open the attached report in EUD
2. Ensure its RuntimeSettings contain parameter "EnableAccessibility" set to True or add the setting before opening the designer in its configuration file
3. Preview the report and export it to PDF


EXPECTED:
The produced PDF is tagged (accessible) - check it in Acrobat Reader's file properties in the bottom left corner. The file size should be ~155KB
OBSERVED:
The produced PDF is not tagged (accessible). Its size is ~123KB.
Completed
Last Updated: 14 Sep 2022 14:06 by ADMIN
Release R3 2022

Some corner case page size value force report processing to create an invalid page clipping during paging. 

Workaround: If you encounter such scenario, please experiment with changing the page size to another value, which is close to the original one.

1 2 3 4 5 6