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: 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.
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
17

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 

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

Using a Toggle Visibility action to expand/collapse recursive SubReport results in the "Node should be found among parent nodes" error. The recursive SubReport renders fine without the action.

The report from the How to represent hierarchical flat data in report recursively - Telerik Reporting KB article was used as a base.

Unplanned
Last Updated: 19 Dec 2022 11:21 by Curt
I noticed that the "Preview" in the report designer within Visual Studio doesn't reflect changes when the source of a  subreport has been edited; it seems to "cache" the first loaded subreport design. 

I made sure that all files were saved and new assemblies have been generated, but the Main Report Preview shows the subreport with the original layout. If I quit and restart Visual Studio, the Preview will then be updated.
Unplanned
Last Updated: 19 Dec 2022 10:04 by Curt

The source of my SubReport was in a nested class and in the preview of the main report I received the error "Invalid report type" although the same nested class was successfully discovered in the VS designer with the assembly-qualified name 'Test.Class1+DetailReport1, Test, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'.

When I tried using a class (without a nested class, e.g., 'Test.DetailReport1, Test, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null') then I could get the subreport to render within the main report.

It could be the syntax for the qualified name is not handling nested classes. 

Unplanned
Last Updated: 06 Dec 2022 12:21 by ADMIN

Make the Design-Time parameter values of the WebServiceDataSource editable through code.

Currently, the design-time values can be edited only by the report designers or by saving the report with the TRDX extension and editing the XML.

In the XML, to change the design-time values, you may edit the ParameterValues property which is a string. 

Unplanned
Last Updated: 06 Dec 2022 10:18 by Keith

In such a case, the following exception is thrown

Inner exception: System.ArgumentException: The path is not of a legal form.
   at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
   at System.IO.Path.InternalGetDirectoryName(String path)
   at Telerik.Reporting.Interfaces.FrameworkDependentDeploymentModel.GetDirectory(Assembly assembly) in

The likely reason for the error is that since the assembly is loaded from the bytes, and not from a path, the assembly.Location in the Telerik.Reporting.Interfaces.FrameworkDependentDeploymentModel.GetDirectory method is Null.

Declined
Last Updated: 02 Dec 2022 12:13 by ADMIN
Unplanned
Last Updated: 01 Dec 2022 08:17 by Aldo
Created by: Aldo
Comments: 0
Category: Reporting
Type: Bug Report
1

In some scenarios, the PrintOnLastPage functionality of the page sections does not work as expected.

For example, if the report with PrintOnLastPage is the last one in the report book, on the last page of the report book, which will also be the last page for that report, a page section will still be rendered even if PrintOnLastPage is False.

This happens when the default PageNumberingStyle.Continue is used by the reports.

On the other hand, if the last report has a PageNumberingStyle.ResetNumberingAndCount, the page section will not be rendered if PrintOnLastPage is set to False, so in this scenario, it works as expected.

Unplanned
Last Updated: 30 Nov 2022 17:07 by Joan
Created by: Mark
Comments: 3
Category: Reporting
Type: Feature Request
21
Dark theme is so much needed.
Unplanned
Last Updated: 30 Nov 2022 10:25 by Todor

I wanted to add some white space between the TOC text and the leader symbols in my TOC. Here is the default TOC when I don't use whitespace:

I tried the following Expression:

= Fields.group1 + "            "

Here is the result - the TOC text of the first level was displaced as if the added whitespace is before the text:

The workaround I found is to add one LeaderSymbol at the end of the whitespace string:

= Fields.group1 + "            ."

Still, it seems that there is whitespace trimming that is not correctly implemented for the TOC section.

Declined
Last Updated: 29 Nov 2022 09:37 by ADMIN
Created by: Patrick
Comments: 1
Category: Reporting
Type: Feature Request
0

Hi,

Have the possibility to have the "Select Case" or "Switch" function in the expressions.

Thanks!

Unplanned
Last Updated: 28 Nov 2022 14:49 by ADMIN
Created by: Danilo
Comments: 0
Category: Reporting
Type: Feature Request
1

The Telerik.Reporting.Report class has the property ExternalStyleSheets which is an ExternalStyleSheetCollection.

This collection consists of objects of the type ExternalStylesheet which has private Name and ResourceKind properties.

Would be great and make sense to make these properties public since that would help when the external stylesheets need to be resolved dynamically, though a custom IReportSourceResolver for example.