When building report templates in the Standalone Report Designer, it would be very helpful to have a keyboard shortcut to access the Property Browser and possibly the other panels (Report Explorer, Data Explorer, Group Explorer).
I have grown accustomed to the shortcuts available in Visual Studio for similar access. For instance, the F4 key will jump to the Visual Studio Properties panel (at least in my configuration) from a designer window. This makes it easy to update things like field name, size, location, and other properties without constantly reaching for the mouse.
Visual Studio uses Control-R to access its Project Explorer (again, in my C#-centric configuration), perhaps similar to the Report Designer's Report Explorer.
Adding these keyboard shortcuts, whether fixed to specific keys or configurable, would speed up report development for keyboard-bound programmers like me.
If you drag and drop a List in a Report in the Web Report Designer, and then reduce its height and the height of its inner Panel from the Property editor, initially, the changes are respected. When you save the changes and reopen the same report, the Panel recovers its previous Height.
The issue is not reproducible when modifying List or Panel size with mouse dragging.
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.
As for now, the workaround is to use the series' DataPointStyle.BackgroundImage property to add a custom image as a marker. Then, to change this image based on the condition you can use DataPointConditionalFormatting property.
The Marker Types I am using are commonly used e.g Square, Plus, Cross. Please add an option to set Marker Type for the values instead of background Image.
There is nothing really pro outside visual controls for reactJs to many source to many projects could be amazing if telerik create this full set including the report viewer
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
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.
It would be really great if there is a Funnel chart.
We are trying to visualize the quantitative slippage in tasks assignment in a given month-range.
We did it very well in SSRS Reporting and as we migrate to Telerik Reporting, we can't quite figure out how to present it.