Our manufacturing floor needs to have unprintable characters encoded in the data matrix in our reports, so that our plant controllers can receive instructions.  The characters I'm speaking about are things like the Record Separator (ASCII 1E), Group Separator (ASCII 1D), and End of Transmission (ASCII 4).  

You can have the three styles in HtmlTextBox. For example:

<strong>bold</strong>, <em>italics</em> , <span style="text-decoration: underline">underling</span>

However, if you use expression, for example:

= IIF( Parameters.Parameter1.Value , "<strong>bold</strong>, <em>italics</em> , <span style="text-decoration: underline">underling</span>","some bold text ")

Then the expression cannot be evaluated and an error is thrown.

I have a Windows Forms application that references a Reports_Library.dll that contains my CLR reports.  I want to use the ReportBook in VS, so I followed all of the online tutorials.  However, I'm having an issue using the ReportBook.  

My Steps:

1. Create a new form
2. Add a Report Viewer to the form (I don't add any report source to the viewer at this time)
3. I add a ReportBook to the form and a dialog box appears with the title of "Report Sources..."  I click on "New" and then I click on "Type name".  From there I click the drop-down under "Select a Report Type" and there are no options...  Usually, when following this procedure with a ReportViewer, there is an option that says <Select Report Document>.  I click on that and then choose my document from the Reports Library.  However, I don't have the option to do that because the drop-down is blank.

When a report is open and the user click on the "generate" button, a busy indicator is displayed and the user can continue to use the application during the generation of the report. The UI thread is not blocked.

But when opening a view with the ReportViewer, the UI freezes during the initial connection to the remote engine, until the report is ready to be generated. If the report has parameters requiring a database query to load the available values, it freezes for a few seconds.

Would it be possible to load the ReportViewer instantly, then display a busy indicator until the report is ready, without blocking the UI thread ? (exactly as for the generation of the report)

Hi,

I would like to know if it's possible to reconsider this request, or at least to leave it open for a longer period of time so people can vote. It would be really nice to be able to integrate existing SSRS reports. We have a lot, I really mean a lot, of SSRS reports. We believe using another third party would just make our "ecosystem" more heterogeneous.

I'm pretty sure we're not alone with tons of SSRs reports that are waiting for a seamless integration with Telerik UI for Blazor.

Thanks in advance

Stéphane Roy

DataPointStyle's initial color is displayed as Black but the color is actually Transparent and if I try to set borders between the data points on my graph, they cannot be seen. 

Reselecting a color fixes the issue.

Exporting a report as PDF produces a corrupted file as soon as it reaches 2GB or more in file size. Available client memory should have been enough and was not at its limit. We have built the application as x64.

We use large-sized image files in the reports.

When using multiple Condition Formatting Rules, the only option is the AND. An OR option should also be available.

Hello,

we changed our reporting service to .NET Core and now the Backgroundcolor for some alternating lines are not visible in HTML5 viewer.

In exported PDF they are...

I change the backgroundcolor from custom like <Style BackgroundColor="240, 240, 240" /> to <Style BackgroundColor="Control" /> which is working fine.

But i can see difference in color of HTML5 report and pdf report.

What can i do to have it working like before, i mean i want to use it like this again <Style BackgroundColor="240, 240, 240" /> if possible.



PS:We are running our service on a Linux Docker-container



Best regards

Thomas

The ObjectDataSource component in the Web Report Designer does not have complete design-time support. The major things that are missing:

• there is no dedicated wizard that helps to discover and select business classes and appropriate data retrieval methods.
• its data schema is not retrieved from the REST service and since it's unavailable, the Edit Expression dialog does not populate its Fields collection.

The Margins property cannot be set in the Blazor wrapper of the Web Report Designer:

One of the main features the clients require when exporting the reports to XLS or XLSX is to have the page width already set to 1 page. But for none of these exporting options, this is possible, unless you intercept somehow the export functionality prior to rendering the document to the client

It would be nice to have 3D chart capabilities such as those found in the WPF ChartView or even the KendoUI charts.  The Telerik Reporting charts , although feature rich, are rather plain looking.

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

We'd like to distribute the standalone report tool to our clients and provide data through a web service. We don't want to have to redistribute a dll everytime we make new data available.

The standalone report tool should be able to query our webservice for what data is available and then allow the client user to create reports from it.  i.e. obtain list of table names dynamically as well as their column names and data.

A possible solution is to allow the tool to view and interact with classes in an external assembly that are dynamically generated with Reflection.Emit.

The issue is caused by an issue in the SQL DataSource Wizard that doesn't provide the correct Data Provider name. In the wizard on the first page, the Data Provider must be MySql.Data.MySqlClient, but the option is limited only to MySql.Data. Since the engine cannot determine the type of the data provider by that name, it falls back to System.Data.SqlClient and claims that "Port" is not a supported keyword.