Unplanned
Last Updated: 09 Feb 2023 07:50 by Florian

If you set the anchor property and validate it, if I come back on the property, the designer does not show the current anchor.

As you can see, anchoring is defined to left, but it is not shown in the dropdown of the property. The anchoring left should be grey.

Completed
Last Updated: 06 Feb 2023 12:40 by ADMIN
Release R1 2023

When a report has a report parameter using a data source, that is visible and has AllowNull set to True, if the value initial value is invalid, no report parameter widget is loaded at all for this parameter.

If this is the only report parameter, the parameters area is not rendered at all, even though the toolbar indicates that it is active.

The issue can be reproduced by loading the attached report in the native Blazor Report Viewer.

Reports.zip

Unplanned
Last Updated: 01 Feb 2023 16:34 by Jim

I have designed a report that includes an embedded SubReport. When I render it to PDF, it looks correct.  When I render it to CSV, there are two issues that are probably related:

  1. The heading row columns should contain the main report's detail row textbox names followed by the SubReport 's detail row textbox names.  However, the SubReport 's detail textbox names are repeated a few times instead of just included once.
  2. In the situation where there is no detail row in the SubReport, a CRLF is missing at the end of the main report's detail data.  The next main report detail data appears on the same row, following the previous main report's last detail column -- it should begin on the next line.

I understand that CSV Rendering is not recommend for hierarchical output as described in the CSV Design Considerations. However, I am using the Hide the SubReport if no Values to not display the SubReport when there is not data. The hidden SubReport implementation can be seen in the below binding expression.

 

<Bindings>
    <Binding Expression="=Count(Fields.AP_OPN_CHK_VCH_NO_C)>0" Path="Parent.Parent.Parent.Visible"/>
</Bindings>

 

Using the above approach, the master report is missing a CRLF when the detail data is not visible. The record shows it appended to the previous record.

I started working with Support on this issue and have discovered that it might be a bug. As a result, I am also attaching their sample to help replicate the issue. For the pdf and csv output see the first attachment in the original ticket.

 

 

Unplanned
Last Updated: 23 Jan 2023 15:48 by Damian

When HTML entities are used in an embedded expression of the HtmlTextBox, they are parsed.

The same does not happen when the "= ..." expression syntax is used.

For example:

This expression works.

= Replace(Fields.Column2, 'less than','&lt;')

This one throws an error.

{Replace(Fields.Column2, 'less than','&lt;')}

 

Unplanned
Last Updated: 23 Jan 2023 08:13 by Hannu

Here is a snippet from the file '/@progress/telerik-angular-report-viewer/dist/es/telerik-report-viewer.component.js' in Telerik Reporting NPM repository of the Angular Viewer that hard-codes the message:

TelerikReportViewerComponent.decorators = [
        { type: Component, args: [{
                    selector: 'tr-viewer',
                    template: '<div [ngStyle]="containerStyle" [attr.id]="reportViewerID" #container>Loading Report Viewer...</div>',
                    styleUrls: [],
                    encapsulation: ViewEncapsulation.None,
                },] },
    ];

Currently, there is no easy way for localizing or removing this message in an Angular-wise approach.

Completed
Last Updated: 20 Jan 2023 12:34 by ADMIN
Release R1 2023
Created by: Ryan
Comments: 3
Category: Reporting
Type: Feature Request
4

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).

Declined
Last Updated: 19 Jan 2023 16:02 by ADMIN

In this file t.folder is lowercase which should be Capital t.Folder

 

t.folder  throws error

 t.Folder return value

 

same or files vs Files

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
Created by: Shannon
Comments: 1
Category: Reporting
Type: Bug Report
4

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.

Unplanned
Last Updated: 18 Jan 2023 00:42 by Sorin
Created by: Erica
Comments: 2
Category: Reporting
Type: Feature Request
33

After reviewing other users questions/issue it appears this hasn't been addressed.

When creating a TABLE group (not a group header/footer) the TABLE group header has no option of displaying on each page when the group spans multiple pages. The advice to make ColumnHeaders = True doesn't help because when you add a group header that row is inserted below the table's header row and thus this doesn't apply to the group header row. 

I'd like to suggust a setting in the table group properties menu to display the header on each page, ideally with an option to display a suffix such as "cont."  

Unplanned
Last Updated: 17 Jan 2023 11:33 by ADMIN
It would be a nice feature to add "Item" function variant that supports dictionaries with string key instead of just arrays with index.

For example:

Item("MyProperty",Fields.MyDictionary)

This would add a invaluable degree of freedom when considering the structure and usage of report's datasources. For example, the current way of working with ExpandoObject (which are also IDictionaries) is very problematic and in my opinion not a good way of doing it. One such utility function will eliminate almost all of the problems that are present at the moment.

Another way (even better) would be to make something like:
Fields("MyProperty")
available in the expressions.

If both ways are added, this will completely (in my opinion) eliminate all the problems using dictionaries and expando objects in reporting.
Unplanned
Last Updated: 11 Jan 2023 10:28 by Sparky

Currently, I am using XmlSerializer to deserialize .trdx file, and it returns Telerik.Reporting.Report type object.

Since, for a long time, I need to add my own functions to be available in the report's expressions, and this need becomes larger and larger, it would be great if I could use the Telerik.Reporting.XmlSerialization.ReportXmlSerializer class to deserialize the .trdx file in my derived class.

For example:

var report = new Telerik.Reporting.XmlSerialization.ReportXmlSerializer().Deserialize<MyReportDerivedClass>(TemplateStream);
Unplanned
Last Updated: 05 Jan 2023 13:38 by Hannu
The Text property of the Report Parameter is localizable and is used as a label for the corresponding parameter editor in the viewers. The localized value is correctly shown in the desktop viewers.
However, the Text property localization is not respected in the Html5 Viewer. The parameter editors always display the Text with the default language.
Unplanned
Last Updated: 03 Jan 2023 09:47 by ADMIN
Created by: Miguel
Comments: 2
Category: Reporting
Type: Feature Request
6

Currently, if the SkipBlankPages property is set to True and there is not any significant content in the report, the following message will be displayed in the designer and the viewer: The current data set presented in the report did not produce any significant content, so no pages were generated. If you need to see the whole report content, including blank pages, please contact the report author.

It would be nice if it can be localized in the viewers.
Declined
Last Updated: 30 Dec 2022 15:28 by ADMIN
Created by: Erik
Comments: 1
Category: Reporting
Type: Bug Report
3
Visual Studio 2022 cannot open reports in x86 mode. The same project works correctly in VS 2019.
Unplanned
Last Updated: 30 Dec 2022 08:52 by Todor
Created by: Todor
Comments: 0
Category: Reporting
Type: Feature Request
4
XML is a well-established format for storing data and it would be great if Telerik Reporting supports it out of the box.
Unplanned
Last Updated: 27 Dec 2022 12:56 by Terry
Created by: Charles
Comments: 1
Category: Reporting
Type: Feature Request
16

We need our reports to have editable text fields where data can be entered into the pdf document and printed.

See also the Forum thread export pdf with editable text areas.

Unplanned
Last Updated: 19 Dec 2022 17:38 by Jose Tuttu

Recursive sub-report with hierarchical data. When expanding/collapsing, all nodes get expanded or collapsed.

I would expect only the selected node to be expanded/collapsed.

For reference, the report from the How to represent hierarchical nested data in report recursively - Telerik Reporting KB article was used as a base