Would it be possible to prioritize which characters can "Break" when wrapping text inside a text box?  For example "foobar/foobar" will not break at the slash, it'll instead break at the character that hits the width limit. It would be my suggestion that punctuation be prioritized for "breaking" before all other characters, in the event that there is no space.

In the attached example, the column headers are dynamic (localized), and there's no way to predict what the text will look like (in whatever language)... Though I accept that no matter what, a string longer than the textbox width will need to break somewhere, I'd prefer that you break on "better" characters if they are present.

(Pretty nitpicky, I know, but this would save me trying to code the logic into an expression or function... which could prove complicated due to variable width of fonts)

We redefining an existing table style (ie. Aspect) in an external style sheet, the user should be able to select the style like now, but disable the style generation in the report file.
Currently, we need to go in the designer.cs file to remove all unwanted styles.

Are there any plans to standardize the shortcut keys in the Report Designer? There are many places where CTRL+C, CTRL+X, CTRL+V, ESC, DEL do not affect the field in focus, but instead a parent window or out-of-context control.

For example:
1. Open the Edit Parameters dialog for the Report Source dialog (In my example, I chose a URL/File and clicked Edit Parameters)
Drop down a parameter name, and hit Escape. Escape is the standard key to close a drop-down. In this case, the "Cancel" button on the dialog is triggered instead. This causes changes to be lost in the dialog.

There are a pile of examples; there's a dialog where pressing delete key does not delete the contents of a field in the dialog, but instead deletes the (selected) field from the report itself; but they don't come to mind right now as I haven't run into them lately.

This is your reply to one of our questions regarding RTL support of crosstab component.
"The Crosstab item will not change its layout (does not support RTL layout flow). You will have to create to separate reports with similar layouts. One report can be used with RTL languages, and another with LTR languages.
Note that row groups can be added only on the left side of the Crosstab item. "
SO our request is to fully supports RTL.

Self referencing parent-child hierarchies (i.e. Manager-Employee) are a common structure, They should be supported in your grouping mechanisms. 

Currently this is only possible thru a workaround as in http://www.telerik.com/forums/cross-tab-report-with-a-self-referencing-hierarchy#7p4BaddGV0iam8J6bT_dpQ

I believe an enterprise reporting tool should support this out of the box.

Thanks,
Henry

Graph should be binded to a single DataModel, but many Graph properties should be then be binded to a specific property of this DataModel:
-each series should be binded to a specific property (which would be a list). These properties would be the data.
-general Graph items like axis title should also be able to be binded to other properties, to allow more complex use. These properties would be the metadata.

As it is now, all the data are put in a single list (not developer friendly at all), and using metadata is impossible.

Currently, the designer automatically increase the width of parent containers when a control is moved or resize and goes outside the current parent size.

But this can be problematic with bad paging in some cases. 
As the automatic grow may be needed, I propose to increase the parent size with a settable minimal step:

When having set everything to have a width of 160 mm, just moving some controls can currently increase slightly the size (like 160.23 mm). But if the report has a minimal grow step of say 5 mm, in this case it will be resized to 165 mm, a visible size difference (therefore, layout can be corrected when the grow was unwanted).

Add a way to force a Page Break in a Multi-Column Report, as opposed to producing a 'Column Break'.
These are 2 separate concepts of a Column Break and a Page Break.

A report viewer feature for SSRS (RDL) so that we can utilize the SSRS 2016 HTML5 in our apps

It will be nice to have a proper (Official) TypeScript definition for the HTML5 Report Viewer. 

Reporting webapi to support asp.net core

The report processor renders a report to XLSX format and adds a BOM (EF BB BF) to every embedded XML file. This is causing some open source libraries to fail to load the XLSX file, which is an issue for some of our customers.

var deviceInfo = new System.Collections.Hashtable();
var reportProcessor = new Telerik.Reporting.Processing.ReportProcessor();
var result = reportProcessor.RenderReport("XLSX", instanceReportSource, deviceInfo);

The work-around is to load the XLSX file in Excel (which apparently ignores the BOM) and then save it (which removes the BOM).

I have read that the BOM is optional (and undesirable for compatibility) for UTF-8 encoded files, which is how the report processor renders XLSX.

Please remove the BOM, or add a Device Info setting "WriteBOM = true/false", similar to the CSV export device info.

Thanks, much appreciated!

Need to support installing and running reporting server restful API from within linux.

As of today, the only way to access the Report definition object from an expression is by using "ReportItem" global object and doing something like this:

  public static MyBusinessObject GetMyBusinessObject(ReportItem item)
        {
            return ((MyReportType)item.Report.ItemDefinition)._myBusinessObject;
        }

It's very inconvinient + it does not work in Parameter's Value/Text/AvailableValues expressions (because there is no ReportItem).

I think, the good and convinient way to work this around would be to have a new global object, named "Report", available in expressions.

It would be great to be able to plot a "Heat Map" style report

Japanese current GS1 QR code format guideline is using binary code for control code like '0x1d', '0x1e', '0x04'. Please check out the attached file. The guideline is compliant with ISO15394(JIS-X-0515). 
Telerik barcode item can print only text now. Then we cannot print the GS1 QR by telerik barcode item.

The ability to add these types of images to reports would be incredible. We deal with numerous companies in the manufacturing sector. These customers have drawings that they would like to print along with their reports (think of a production order to build something, we show a list of the materials to use and the drawing/cad would be required).

We create many legal forms, which use nested ordered lists. In htmlTextBox for reporting, we'd like to apply styles like upper-alpha, lower-alpha, etc to the ol tag. Currently, the only numbering for an ol is 1, 2, 3. CSS ability to set the style at depth (like ol ol) would be best.
<ol>
<li>1. text</li>
<li>2. text
  <ol>
  <li>a. text
     <ol>
          <li>i. text</li>
          <li>ii. text</li>
      </ol>
  </li>
  <li>b. text</li>
  </ol>
</li>
</ol>

In the Configure Object Data Source Wizard, add a method of filtering the displayed Business Objects.
Where a large number of Business are display, scrolling can be painful to find the required one.