Nested OLs do not start with the number of their parent but instead, start counting completely anew.
Offer a solution allowing nested OLs to generate this form of rendering.
1. title1
1.1 subtile11
1.2 subtile12
2. title2
2.1 subtile21
2.2 subtile22
2.2.1 subtile221
2.2.2 subtile222
2.3 subtile23
3. title3
I have a request that probably doesn't require much explanation. It would be helpful to allow comments in expressions created via the standalone designer to help explain particularly complex and infrequently encountered logic.
Our team is in the process of converting Crystal Reports documents over to Telerik Reporting and one of Crystal Reports advantages over Telerik Reporting was the ability to create custom fields with Crystal or Visual Basic Syntax, including the declaration of variables. Lack of variables and a few common constructs can make simple expressions overly complex.
One of the more common use cases for us is formatting text differently based on one or more other values. Without the ability to write if/elseif/else blocks we wind up with nested ternary statements which can be are hard to read and maintain.
While we can write user functions that seems impractical for long term maintenance and support. It would be very helpful if we could create expressions using C# directly in the Report Designer and have the embedded within the report itself.
See my initial request for something similar in the forms here: https://www.telerik.com/forums/feature-request-if-elseif-else-and-or-switch-statement-support-in-expressions
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).
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.
As I outlined in my Issue with the Cross-section Item post to the forums, the current implementation of the cross-section item carries the following limitation:
The Cross-section item uses the report's data context and cannot be evaluated against detail or group data. The processing engine produces a single instance per each Cross-section item in the report definition, therefore its style or visibility cannot be changed based on data fields.
For invoice (or sales order) style reports this places a severe limitation on the complexity of the report.
One of my current projects requires me to create a report layout that can be run for multiple invoices from multiple customers, where each customer has their own unique set of flags that control what information is included on their invoices for each line item of the invoice.
My current version of this report works great when it is run for a single invoice or invoices from a single customer (or from customers who use the exact same set of print flags) by binding the visibility and begin/end margin values of the lines that start in the groupHeader section, cross through the detailSection, before finally terminating in the groupFooter section.
This can be seen clearly in the 2 attached invoices, one with lots of columns of information (called: Invoice with lots of detail columns.png), and another where the customer has been configured with all the additional information toggled off (called: Invoice with minimal detail columns.png).
Unfortunately, because of the cross-section item's current limitation, when I run the report for both invoices the lines attributes/visibility are set based on the customer flags of the "first" invoice in the group, and do not get reset for subsequent invoices. This can be seen in the attached file: Behavior when including both invoices.png.
I understand that if a cross-section item begins/ends in a page/report header/footer, then having it's attributes change based on group-specific data would be less than ideal. But when the line beginning and end points are restricted to a group header and footer, as it always would be for a report layout used for multiple invoices or sales orders, then having that line's attributes change based on the data is the only way to use this functionality for these types of complex reports.
NOTE: While there is a workaround using the attributes/visibility of detail columns, vertical lines in the detail section, and their associated headers and totals textboxes in the groupHeader and groupFooter, it results in an unprofessionial looking report because of the difficulty in getting the variable border and detail vertical lines to line up precisely (and it is very time-consuming to try to implement).
SUMMARY:
Changing the Cross-section item implementation to allow it's data context to be evaluated against detail or group data when the line's terminators are restricted to groupHeader/Footers would allow for its use in more complicated report layouts.
BTW: interally, we refer to these reports as Mighty Morphing Invoice Reports™!!!
It would be great if you could make the border of the stand alone report designer visible. It's hard enough to see and grab thin gray lines but Report Designer borders become invisible. Below is a screen shot of the report designer in front of my Telerik Reporting program folder:
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.
If any schema other than dbo is used, the report viewer throws the following error:
Error registering the viewer with the service
Could not find stored procedure sp_tr_GetString
When a report includes drill-down item(s), the report is run again each time the user expands a drill down item. This is apparent in the demo at https://demos.telerik.com/reporting/product-sales
I would like to see all of the drill-down data generated and delivered with the initial report, but collapsed and awaiting inspection.
Perhaps this would be an attribute of the drill-down element (pre-fetch versus re-run) so that developers can choose the most appropriate experience for their users / conserve server resources.