Hi there, It would be nice if the vector images included in reports could be preserved when exporting as a PDF. I have some emf images which I use in our reports and when viewing everything is lovely vector, as soon as I export it though the image is converted to a bitmap.
As a developer that uses both Telerik Data Access and Telerik Reporting in its projects, I often find myself in a situation where I experience version mismatch errors regarding the Telerik.OpenAccess.* assemblies. For me it is inconvenient to downgrade the version of Data Access, and would like to either be able to automatically add the binding redirects in the .config file, or to use a more recent version of Data Access in my Reporting applications.
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
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.
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.
When converting Crystal Report templates (rpt files) to Telerik Reporter templates it would be very helpful to include the schema settings in the associated ttx file which provides the dataset info. This allows the layout to map properly to the converted template. Also any imbedded SQL statements found in the Crystal template could be captured and the conversion wizard could then query the developer on database connection requirements. These two abilities would make conversion a complete tool allowing rapid deployment of new Telerik report templates.
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.
Ability to make a column in table or crosstab having width based on its content
When you have your .trdx and external stylesheet files in a separate directory (e. g. a server directory available to all workplaces) it gets very difficult to show the .trdx files in ReportViewer without manipulating the reports a lot by code. 1. The external stylesheets are searched in the bin\Debug directory of the main application when using Kind="Relative". 2. What is even more annoying is the fact that all SUBREPORTS are also searched in the bin\Debug of the main application. I have to recursively look through all report items if there is a subreport and set its location. It would be very nice if the ReportViewer supports some kind of "path-to-reports" property and locate all the dependend files like subreport or stylesheet in this directory.
It would be nice if the parameter window to enter Report parameters in preview mode would remember the last values entered between invocations.
It would be good to use an expression to display visibility, so 'True', 'False' and Expression. The expression would just need to return a string value ("true", "false", "True", 1 etc.) that is passed to a bool parse and throws an exception if the expression can't be parsed.
The Standalone Designer allows a template to be loaded from a .NET dll. Add the ability to load a template from a .NET exe.
The ability to use static values and display members as an array for a multi value parameter. I want my team to be able to use the standalone report designer without a custom User Function or a data source. We had been using SSRS and made a switch to Telerik, and this seems to be the only hangup that we are unable to convert cleanly.
On opening the Expression Editor, if at least one Data Source is present on the Report, then the Fields item in the tree should automatically be selected. If no Data Sources are present on the Report, then the default selection should be the Report Parameters.
With reference to support ticket 992325 where the behaviour of making minute changes to the measurements of grid columns occurs inadvertently I would like to suggest that this is changed and does not happen, i.e. improve the handling of floating point numbers in the serialization/deserialization process. It causes noise in the source control history of the file. Note that this behaviour is not apparent with comparable reporting solutions, e.g. SSRS/RDLC files.
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 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!
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
Please consider giving the possibility to reload a report prepared and stored to disk in the report viewer at a later time.
It would be very useful if custom size and arrangement of the tool panes could be remembered by the Standalone Designer. In particular it would be useful for the property pane and it's popup windows (e.g. Graph Series Connection Editor) More info here: http://www.telerik.com/forums/remember-user-settings-between-opening-and-closing-the-application