Create new parameters control (as same included in report viewer controls for WebUI, WinUI, ...); to provide the ability to gathering user values but without rendering the report.
It will help scheduling and background generation of reports.

Currently, we need to set the Height of the container to a very small value to collapse it to its minimum size when some children aren't visible.
This need to be made in code behind, or via binding, and we need to do it for each container which can have children (direct or indirect) hidden. Not developers friendly at all.
And this only work if the contain itself is always visible, otherwise no correct collapsing will be made (Telerik told me that "The space taken up by a panel item will be collapsed when the panel is invisible based on the panel's initial height.")

A container should always be collapsed to the height taken by its visible children. When someone want to have an empty space, he should use padding, not the height of an invisible item.

Presently, when you use the Fields property, you can only access simple type properties : "= Fields.CompanyName", "= Fields.CompanyPhone". The complexe types are not accessibles via the Fields property. If you want to print a complexe type property, you need to use the expression "= ReportItem.DataObject.Company.Name", "= ReportItem.DataObject.Company.Phone".

In my opinion, this is not very intuitive. 2 differents ways to read a property depending of his type! It would be great to be able to access anything from the Fields property.

Need a way to export a drill down report with the visibility toggles as they are set in the Reportviewer.

Currently, if row visibility is something other than the default, if you export a report using the suggessted method:

Dim result As Telerik.Reporting.Processing.RenderingResult = _
		reportProcessor.RenderReport("PDF", ReportViewer2.ReportSource, New Hashtable())

Using fs As New System.IO.FileStream(filenamePDF, System.IO.FileMode.Create)
    fs.Write(result.DocumentBytes, 0, result.DocumentBytes.Length)
End Using
 
It loses the user defined visibility and exports the default.

If you use the Reportviewer.ExportReport() call, the report retains it's visibility, HOWEVER it prompts a file save dialogue. Unfortunately we cannot allow file browsing for our clients.

If we simply had an option with ReportViewer.ExportReport() to specify the file path to save to (preventing the file dialogue from popping up), this would be a non-issue.

Currently, if you wish to hide extra details on the second page of a report, the space taken up by the area is left blank which looks terrible and not conducive to professional report design.  

Related threads:


http://www.telerik.com/forums/different-page-header-on-first-page

http://www.telerik.com/forums/hiding-the-page-footer-leaves-a-blank-space-in-the-report

Unfortunately using report books for this is not a valid option.  Using the Report Book means quite a bit of extra work when all you need is for the second page to not have an glaring empty space.  If I understand the process correctly, this means creating 2 reports which are nearly duplicates plus merging with Report Book for each 1 report that you are developing.  This is unresonable to expect from enterprise shops that will develop hundreds of reports.

I urge you to review your implementation in order to find a way to implement this feature in the future. 

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.

When might Telerik come out with a standalone reporting tool?

we have the ability to conditionally display a label on the x-axis.  Thereby displaying only some x-axis dates, for instance, but not all of them.  Can you enhance the product to allow for the displaying of tick marks only for the values (dates in this case) displayed?

I'm planning to use Telerik Reporting as the reporting soltion for a customer portal that I'm developing. This portal will be sold to multiple customers and amongst other things the customers will be able to add their own reports that they will build using the Stand Alone Report Designer.
Please consider adding a Query Builder, similar to what is in the Visual Studio version of the Report Designer to the Stand Alone Report Designer as this will greatly enhance the user experience and negate the need to use other tools to build the queries, especially as many end users would not have access to tools such as SQL Management Studio, etc.

Regards

Edu

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

I've been using the Stand Alone Report Designer a fair bit lately but find myself having to switch between the Home, Insert and Data tabs quite a bit. It would be a great time saver if the Report Designer had a dockable toolbar (defaulted to the right) like in Visual Studio with short-cuts to adding things like Text boxes, pictures, etc.

Regards

Edu

It's confusing which rule does what by looking at the current UI...would be nice to give them aliases\friendly names which mean something when you go back 2 months later, know what I mean?

It would be nice, if not required by our client, to have 100% Web-based, Rich, Ad-hoc Reporting Solution.
Something similar to the one in ComponentOne Active Report 

Please add support for Data Matrix barcodes.  As of Q3 2014 this is the only format we will still need to rely on another library to create an image that is placed in a picture box.  We would much rather be able to use the Barcode control for all our barcode requirements.

When using multi-child select statement like the below:

SELECT ORG, C1, C2, ... FROM (
   (SELECT X FROM Y WHERE Z1 = xxx AND Z2 = :param1 AND DATE BETWEEN :param2 AND :param3) C1,
   (SELECT X FROM Y WHERE Z1 = yyy AND Z2 = :param1 AND DATE BETWEEN :param2 AND :param3) C2,
   ...
)
Then binding with report parameter will be like:
param1 = rpt_param1
param2 = rpt_param2
param3 = rpt_param3

The an error occurred while excuting the query in the datasource wizard.
Also, some time the wizard accepts the query but the preview mode will display the same error.
The error is "ORA-01008 : Not all variables bound"

______________________________________
Workaround: Don't use the same query parameter in more than one child select statement. Create new datasource parameters per each select statement; then bind them all to the same report parameter. 

SELECT ORG, C1, C2, ... FROM (
   (SELECT X FROM Y WHERE Z1 = xxx AND Z2 = :param11 AND DATE BETWEEN :param12 AND :param13) C1,
   (SELECT X FROM Y WHERE Z1 = yyy AND Z2 = :param21 AND DATE BETWEEN :param22 AND :param23) C2,
   ...
)
Then binding with report parameter will be like:
param11 = rpt_param1
param21 = rpt_param1
param12 = rpt_param2
param22 = rpt_param2
param13 = rpt_param3
param23 = rpt_param3
______________________________________
Products:
* Report Designer v2014.Q2
* Oracle Database 10g1, 10g2 or 12c
* Oracle Client: ODTwithODAC 12.1.0.1.0 Or Less

When opening a data source by the wizard and go through it then save (even without any modification), the provider property will be cleared.

Workaround: Re-set the 'Provider name' again upon closing the wizard, by the properties window.

Product: Report Designer v2014.Q2

The date format of the report parameters is related to the culture, but the data source parameter is not.

Add Right to left attribute to the three levels of the reports, with default 'inherited' of child levels:
Level 1: The report document
Level 2: Report Section
Level 3: All type of object and controls including Table/CrossTable

In the attached photo, I combined the first 2 pages of the PDF I get when I export the reports as a PDF (there were 198 pages in total). The second page is the continuation of the bar chart, as the bars expand. This is not readable or insightful to a user who wants to view the report, as he/she can not see any of the labeling of the X or Y axis on the second page. I would like to see labeling of both the X and Y axis on each page, so that the reports are easier to read. The same applies for graphs, columns, and table reports as well. 

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