We would like have two options when we use the date time parameter in report. 
one is only date, other one is date and time. and we need to provide the format to the date time parameter for internationalization.

As our business requirements are very strict we need to be able to set the Graph Scale Maximum and Minimum properties based on our data. This would make our charts much more visually pleasing having the needed empty space above the data.

For example, the most often required scenario is setting the Scale.Maximum as a percentage of the already calculated max value by the Telerik Reporting engine.

We imagine there would be some kind of object which we can use inside an expression in these properties: = CalculatedMaxValue * (1 + 0.1)
Or we can calculate the value ourselves inside a User Function and then use the function in the expression.

I'd like to suggest that the behaviour (positions the viewer at the top) used for alternating between the bookmarks to the Report Header and Group Header using the document map, be applied to the Page Header too. It would be better, if the viewer always started at the top of the first page when using the Page Header.

Bug Report ID: 902125 -- Scroll Top when alternating between bookmarks

About the attachments:
-OriginalReports - these files show the reports without clicking on the bookmarks
-ReportScrollTopBetweenBookmarks - these files show the reports after clicking on the bookmarks

Allow custom buttons and other controls to be added to the existing ReportViewer Control Toolbar.

When using multiple Condition Formatting Rules, the only option is the AND. An OR option should also be available.

Ability to localize Standalone Report Designer created reports without the need of using custom functions.

I would like to be able to do this syntax: Fields.Address?.State.  If address is null, then it is the same as state being null.  Instead of displaying an error, it would just show blank.

I need SVG background images which are rendered as vectors to PDF (not rasterized) - just like with PictureBoxes.

When designing reports with lots of parameters (which is very common for my usage), I often get error message "Missing or invalid parameter value" or "Syntax error in expression". I find it very time consuming and annoying to manually check "all" parameters in order to identify which one is causing the issue. 

Would it be possible to include more details in these error messages, e.g. by including the name of the (first) incorrect parameter? Preferably for the message in report viewer / preview, but at least in the log file.

 

https://www.telerik.com/forums/missing-or-invalid-parameter-value-please-input-valid-data-for-all-parameters

Please provide the possibility to localize the HTML5 Report Viewer UI in a way that doesn't require modifying the template.

It's already possible to localize the messages shown by the HTML5 Report Viewer as shown here: http://www.telerik.com/help/reporting/html5-report-viewer-localization.html
Something similar for the actual UI would be great.

For Clustered Column graph should be some feature allowing to mark zones, something like marked zones.

I need to customize the standalone Report Designer. I distribute it with my own product and I need to replace the title of the standalone ReportDesigner with my brand. 
For example DevExpress report designer allows that. 

It would be nice if we can set ToolTips for the report parameters in design time

Much like the way Excel has the ability to utilize VBA functions. it would be usefull and more conventient for developer if they could include custom functionality/functions in a report rather than use an external assembly.  The steps involved to include/use an external assembly is daunting at best and not at all straight forward.  

Something like you right click the report and one of the menu options is "Add Custom Function".  Or in the expressions dialog box have an option to create/add a custom function.  

You get the point.  I'm sure your team of developers could come up with something. 

The report engine calculates firstly how many rows will be necessary to accommodate the cell content and then the binding is taken into account. For example, if initially 2 lines are needed for the value of the textbox, the final cell height will be equal to two lines although later the width will be increased and the text will fit in a single line.

When using a report parameter of type Float, and there is no value for decimal places, or it is 0, it appears as if the parameter value passed to the runtime is converted to an integer value, and an "Invalid value for parameter <paramName>" is logged. 

We are using the external style sheet file (StyleSheet.xml) when designing our report from Web report designer. We want to see our style sheet applied on our report when we see the report from Web designer in design mode. In Preview mode it is working fine.  But the problem here, it is not working in Design mode.

See the attached pictures. You find our problem on the picture ExternalStyleInWebDesigner-DesignMode.PNG

Is there any solution or a feature request needs to be created?

FYI: External style sheet is working in Standalone report designer in both design and preview mode.

 

Thanks,

When the PDF rendering extension has its "enableAccessibility" setting set to true, the text in the produced document cannot be selected using the Select Tool from the Adobe Acrobat Reader context menu. The text can be selected in other PDF readers like Foxit PDF Reader. The text is also selectable in Adobe Acrobat Reader when the document is created without enabling the accessibility features.

I have a Crosstab with multiple dynamic detail columns and a Total column at the end. I can hide all the detail columns conditionally, based on a parameter value. The Totals are always visible. When there are more than two detail columns and I hide them, there is blank space left between the row headers and the totals of the crosstab.

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