The standalone designer throws an error, e.g. "Missing operator before", if you make a mistake in the conditionalFormatting expression and close the expression editor.  You are then unable to correct the mistake without opening the trdx in a text editor.  Please change the behaviour so that the editor can still be opened even if the expression has syntax errors.

Add support for the <pre> tag.  This would allow content to be added to the HtmlTextBox without having to worry about encoding it properly.  We use the HtmlTextBox frequently in situations where we want to apply mixed formatting.  

This would help in several scenarios.  One scenario that came up recently was when I wanted to render literal space.  I got around this by replacing every other space with a non-breaking space but the pre tag could have made this much easier.  Other situations involve getting text from the database that could include a < or > symbol which we have also got around making sure we run the text through an HtmlEncode routine.

When I select a column in a Crosstab and set a Binding for a Property (for example Visible) it will overwrite all existing Bindings for all Textboxes in that column without any warning. This shouldn't happen. At least there should be a Message that you overwirte existing Bindings and ask if you really want to do that.

Graph markers, it would be nice to have a few more marker types for the chart, I would really like a up and down arrow, or a reversed triangle. also a left and right arrow/ triangle, and how about a star?

Please add ability to show vertical line markers on a Line series graph as show in attached file.

Having a white background in a view when using the dark theme is very bad for the eyes.
You should check all your UI in Visual Studio, as I already asked in the past for a correct context menu for dark theme (now done).

Looks like if print in windows service will be has some problem , because print in windows service can't display the print dialog.

The order of the items in the Border Style Properties should be changed such that Solid is the second item in the list, after None, as this is the most frequent option. This would allow the Border Style to be changed to Solid with a double-click.

Add the functionality of the Page Up/Down as well as Home and End to the WPF Viewer Control, so that the displayed page may be controlled using the keyboard.
These buttons should also work with the CTRL+ variations.

I am using Telerik Reporting with MVC 5, and would like the ability to use the custom parameterEditor with MVC. If anything, I'd like to be able to create it with razor MVC, and then use jquery to add the parameterEditor.

Currently, the size and location of items displayed in Properties view are rounded value, but the real value written in the .Designer.cs isn't rounded at all.

This created some imprecision in size and location, possibly resulting in unwanted resizing of the report width, or in overlap.
Now, it is only possible to correct this in .Designer.cs, and the user don't see the problem without zooming at maximum or opening the .Designer.cs

Rounded value seems better than some unneeded decimal, but then the value displayed should also be written in the .Designer.cs

In general I quite like the Stand Alone Report Designer but one thing that is a bit painful is that the default height of new fields are way to big. About half the current height would be more appropriate. It wastes time to have to resize every field after adding it, and especially also having to also shrink the height of details section is you added a new field to it.
It would be ideal if you could add a configuration section where everyone can specify their own default values such as field height but page size would also be handy.

Thanks for a very handy product.

Regards

Edu

Adding support for label connectors. This little line that attach the label to his part in the chart like the ones from Kendo UI: http://demos.telerik.com/kendo-ui/pie-charts/index

We had a pie chart with 9 slices with limited plotting space. The labels are overlapping and random at best and not presentable at the moment. 

We tried the following scenerios:
  ThisPieChart.IntelligentLabelsEnabled = true;
  ThisPieChart.AutoLayout = true;
  Alternate the bigger slice with smaller slice to give good space for labels.
  Printing out in Black and White paper also is a mess as patters are not there on the slices.

Hi, for our coming cloud platform, we need a Report Service Engine which is capable of deliver Reports at a scheduled time to specific users in per ex: inbox or folder or etc...

Some of your competitor like ComponentOne seems to have already these kind of feature: http://www.componentone.com/SuperProducts/ActiveReports8Server/Server/

I would honnestly work with you guys so, I would love to see these kind of stuff in near future....

Txs
-Vince

ps. you may contact me for any question for more details or I would be part of any preview of beta ...

Actually, the report footer displays right after the preceding content. It would be very useful to force it to the bottom of the page, just before page footer

When using report templates, the only connection with the original template is when the report is created. This is problematic due to the time it takes, as well as the potential for error and inconsistency.

It would be helpful if the report designer included an ability to update a report based on the template. If a minor change needs to be made to a group of reports, now that change has to be done individually in each report. Ideally there should be an option to update the report from the original template. While I understand that detailed content would be problematic to update, things such as styles, report and page headers/footers, etc., could be updated (or 'replaced' with the equivalent content from the template). 

Ideally there would be an option to update from template, and then the user could select which items to update; 
- styles
- page header/footer
-report header/footer

Datasources of tables and expressions are processed even when the item is not visible. This can lead to performance problems. It should be possible to disable certain items to be processed. The most obvious way is that items are not processed, that are not visible anyway.

The interactive view is excellent for providing a full list of rows in a table but sadly it’s not easy to break that result into manageable pages.  If, for example, we have a large table list that isn’t readily breakable into sections, the resultant large table will cause most web browsers to consume a large amount of RAM and suffer performance loss.  It would seem sensible to have the ability to force a page break when the interactive page reaches a certain size.  This way it would reduce the amount downloaded into sensible page sizes and ensure the browser is not overwhelmed.  This would be very similar, I hope, to that already provided by the print preview mode which breaks on the print page size, all we need is that functionality for interactive pages but via a separate ‘Interactive Page Size’ property.