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.
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.
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.
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.
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."
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")If both ways are added, this will completely (in my opinion) eliminate all the problems using dictionaries and expando objects in reporting.
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);
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.
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
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.
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.
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.
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.
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.
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.