Reporting webapi to support asp.net core

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.

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).

The ReportFooter does not print at the bottom of the last page if that page doesn't contain data, even with PrintAtBottom=true set. Can this feature be changes to always print the ReportFooter at the bottom of every page?

just the same like here
https://www.combit.net/en/reporting-tool/pdf-object/

Add a Property for all controls to be able to set whether the control appears on every page of the report. At present the entire Group Header/Footer may be set to appear on every page, but not just a single control.

We required a Barcode and ID. No. to be displayed on every page of the report. It has been really complicated to utilise a series of Group Headers and Sub-Reports to achieve something that should have really easy. The layout of the Report could not be modified as it is set by Government.

Telerik Reporting should facilitate turning the complex into the straight forward.

I find it extremely limiting and frustrating to not have control over how the .NET Report class is initialized, and not being able to pass in any type of object/dependency (either into the constructor or by setting a property.) This makes it very difficult to keep custom reports decoupled from other code modules and make them unit-testable. 

There is the InstanceReportSource, which would have been perfect to solve this problem, but it's apparently deprecated.
http://docs.telerik.com/reporting/t-telerik-reporting-instancereportsource

DevExpress reports for example allow you to create the report instance yourself, and you can pass any objects you want directly into the constructor. 

This is what I find to be the biggest drawback to Telerik reports. 

Currently, adding Sparklines (http://docs.telerik.com/reporting/sparklinesanddatabars#sparklines) or Data bars to the report requires manual formatting of the Graph item (hiding the Axes, Labels etc.).

Let us know if you think the built-in support for this type of chart would be useful when creating reports. Please share your ideas/thoughts in the comments and give a vote for this feature to support it.

An example of Sparklines/Data Bars is provided in our online demos - http://demos.telerik.com/reporting/product-sales?&skinName=silver(Product Sales report).

Thank you.

Please support OData services as built-in report datasource.

We would like to use Telerik Reporting and Report Server but the missing support for OData is holding us back.

Let us know if collapsing report sections in report designer would make the designing of reports more convenient for you.

When reports have more complex structure with a lot of sections collapsing some of them might improve the overall design time experience.

As a reports user I would like more options for Line Styles in Chart plots.
Currently the options are Solid, Dashed and Dotted.
As a start it would be great to replicate the options in the Kendo UI Line Charts dashStyle enumeration:
https://docs.telerik.com/kendo-ui/controls/charts/chart-types/line-charts#configuration-Types

As the perfect option list for me:
Solid
ShortDash
ShortDot
ShortDashDot
ShortDashDotDot
Dot
Dash
LongDash
DashDot
LongDashDot
LongDashDotDot

Thanks

Currently the images loaded in PictureBox item and Style's BackgroundImage property are rendered preserving the item's physical size. This causes scaling when the machine's DPI is different than the image DPI and affects the image quality.
A specific option should allow the images to be rendered without being altered, including applying antialiasing on the target graphics object.

The Labels to be displayed on a Numerical Scale Axis are currently set automatically.
The user can control the scale range via Axis Scale Minimum and Maximum properties. The user can control also the Label Step.
However, the exact Axis Labels to be shown are calculated automatically and cannot be controlled directly by the user.
For example the user cannot force the Axis Labels to start from the Minimum value.

Please provide an option to launch a sub report directly from within the main report designer (standalone version).
Example, in Crystal reports, if there is a sub report within a report, a user can double click that sub report and it opens it as a new report tab. This is very convenient rather then having to chase down the path to the subreport and open it manually.

I have a report that has dynamically created html text based on the data. I would like to have a footnote associated with one of those HtmlTextBox controls to appear at the bottom of the page on which the section occurs.
Please see a ticket "How to create a report footnote"  https://www.telerik.com/forums/how-to-create-a-report-footnote

Thank you.

Add intelligent code completion in the Report Designers Expression editor to improve the editor usability and user experience.

When the Name of a Report Parameter is changed, all references to it should be automatically change.

So there is an Angular report viewer of sorts, but the report viewer web api component doesn't work with .net core (must target 4.6.1) and the angular component doesn't work with universal/server side rendering.  It would be great if this could get fixed!

Do you have an updated road-map or plan to support Web assembly (WASM), especially Blazor? You already published Blazor articles in your blogs.

It will be a good idea to add a new report viewer based on Blazor, protecting the parameters between the viewer and its API controller.

Also, will be a very good idea to start your online report designer (like alternative products), based on web assembly