Currently, when I create a report with the Standalone Designer and localize it, I can preview it only with the language of the machine where I run the designer.

It would be very helpful to have the option to select one of the languages I have set up during localization when previewing.

In my report, there are multiple stacked Panels. Each of them may fit on a single physical page. They all have KeepTogether set to True and I expected each of the Panels to start on a new page as two of them cannot fit on one page. This may not happen when I have Page sections though.

When I delete the PageHeader and/or PageFooter the Panels are displayed as expected. However, if I set the Visible of the Page sections to False, the problem persists.

It looks like the Page section's Height is taken into account when evaluating the KeepTogether behavior even for the pages where it is hidden. This shrinks the available physical area and the Reporting engine decides that the Panel cannot fit there, hence the next Panel starts from the current page rather than the next page as I think is correct.

It would be great if you could introduce the ability to create custom reusable color palettes in Telerik Report Designer, so I don't have to declare the same set of colors for each chart I need them.

If you have a lot of graphs in your report then it is more convenient to change the color palette one place.

I have a table with a dark background. In some scenarios, one or more data source fields may be empty, leaving the corresponding table cells with no content. When I export this report to DOCX, the empty cells contain strange white lines.

In the other export formats, the issue does not occur.

Here is how the table looks like in Word:

Product: Telerik ReportServer 8.1.22.622 ( 2022 R2 SP1 )

I can't delete any report file (.trdp) after being uploaded to Telerik Reports Server (Web Management).

When I click delete an error message says 'An error occurred when trying to delete report, can't connect to agent service'
but the reports agent is running well and other commands like (upload report, rename) also work fine except for Delete.

So I had to delete the reports server's storage folder (~\Data), setup everything again and re-upload all my reports again each time I want to delete a report.

If you would please fix this critical problem in the next versions so I can use Telerik Reports Server again.

Please fix it ASAP. Thanks

• The Report Viewer component is not correctly creating DateTime type fields. It renders them of type textbox.
  The current version of the Telerik Reporting library is: 16.2.22.914.
  We use Telerik UI for Blazor 3.6.1.
  We are using the Telerik.ReportViewer.Blazor library

On the last step of the SqlDataSource Wizard in the Web Report Designer, executing the query to preview the records displays the columns with a lowercase character at the beginning which can be confusing.

After the wizard, the names of the columns are correct and can be used as expected by the designer.

We are using Telerik reporting R2.2022 version in our project. Some of our reports have html link (created with tag “a”). If we preview those reports html link doesn’t act as an actual hyperlink, so it’s not clickable. We know that there is a HtmlTextBox limitation not to be interactive in WinUI report viewer. But this is important for us to be able to click on html link on WinUI and we need that functionality.  

I tested WinUI example project (CSharp.WinUIExample.VS2022.sln) and opened SwissQRBill.trdp report. The report has some links to the external source in internet, which is not clickable, but if you open it in Standalone report designer it’s clickable.  

Is it on your roadmap to implement that feature? 

Thanks,

Hello

I have a problem with report generating. We use HTML5 report viewer and basic implementation of ReportsControllerBase on server.
I've noticed that we have the CPU/memory recourse consumption after immediately pressing Stop Rendering button. The time of consumption recourses is the same as time without cancelling(about 18-20 second in my example)
There is log with calls of report generating. Last one with cancelling, previous without. 
(see
*** ReportProcessor.ProcessReport DONE in 00:00:16.1918150 ***
and
*** ReportProcessor.ProcessReport DONE in 00:00:16.8522950 ***)

I've investigated how cancelation is working.
The Stop Rendering button send DELETE request to ReportsControllerBase.DeleteReport endpoint. It does something and set IsDeleted flag for document.
Then DocumentCancellationController.ThrowIfCancellationRequested() is called in some specific places in app. You can see that method in log.txt, so it was called after pushing the button.

I've profiled the hot path of generation of report. See hotpath.png.
The most CPU intensive work happens in ReportProcessor.ProcessRepourtSource()...
Pay attention to rendering calls.png - the first red dot here - ReportProcessor.ProcessRepourtSource() call.
The second - where the exception and actual cancelation happens.
I'm expecting it should happen much earlier and cancellation of generation of document(and resources consumption) will finish ASAP.

By the way, I see some cancelation checks in ReportProcessor.ProcessRepourtSource() as well - see throwIfCancellation.png
But cancelation request came after these check and most intensive CPU works already started.


Is it possible to fix that?

The issue may be observed with the online demos - see the linked screenshot.

If I go back and add new records, the total rows count gets updated but still doesn't count the initial rows.

As explained in this support ticket (https://www.telerik.com/forums/specify-default-print-settings---number-of-copies), our customers want to be able to set the default value of the number of copies for a report since they require multiple copies for their business processes.

Would it be possible to enable setting the default values for the printing when a report is generated?

New development is being done with net core 3.1 and netstandard 2.1 and we can no longer create reports in the Report Designer using the ObjectDataSource.

Seems like it's time to update the standalone Report Designer for these new standards.

Problem description:
On ".net Framework" it is a supported scenario that assemblies with datasources and/or functions are loaded into the standalone ReportDesigner. This assemblies are used while designing and later also in the ReportViewer while executing the report. Feature described here https://docs.telerik.com/reporting/standalone-report-designer-extending-configuration

Now that .net 6 is release by MS the same feature is needed there. The problem is that the "standalone ReportDesigner" is targeting ."net framework" which means it can only load assemblies targeting ".net framework" or up to ".net standard 2.0". But that is not sufficient because on ".net standard 2.0" only EntityFrameworkCore3.1 is supported and all newer version (EF Core 6.0) are not.  See here https://docs.telerik.com/reporting/knowledge-base/use-reporting-in-dotnetcore-with-entity-framework-core

So in summary:
It`s not possible to use EF Core 6.0 (and upwards) DataSources in the given "standalone ReportDesigner" because it is targeting .net framework. It`s critical to be able to use the newest EF Core versions as DataSource to not be blocked from upgrading a ".net framework" application to .net 6 where the described feature/scenario is used. I need to use the "standalone ReportDesigner" because it gets shipped with the application to edit the reports individually by the enduser. The "VS ReportDesinger" is going to get the upgrade but this would only be usable as a developer before shipping the application.

Feature request:
Upgrade the "standalone ReportDesigner" to target .net 6.

When a TRDP/TRDX report is imported to a CS report, the produced .designer.cs does not have Unicode encoding, instead, it is with ANSI encoding.

Because of this, some of the report text might instead be displayed as ????

The workaround is to Save As the file, from Visual Studio, with Encoding which will open a window where you may change the encoding to Unicode.

Steps to reproduce the problem:

Some corner case page size value force report processing to create an invalid page clipping during paging. 

Workaround: If you encounter such scenario, please experiment with changing the page size to another value, which is close to the original one.

The following Base64 image:

iVBORw0KGgoAAAANSUhEUgAAATIAAABaCAYAAAA7FtpGAAAABHNCSVQICAgIfAhkiAAAAZ1JREFUeJzt1EkOgkAAAEHw/3/Gk9HoIEsksZOqm8wCDtrzNE3L9GJZnh/nef649j62Zu+a0bzR/Me80bWttXuf6ej3PHNWZ85y7V6j8T17nd3v6LtaG79q3mj+0fdy9Pz2/g/OzLvqHLf2+MUZfPutbN1j6/2N1t6+PyrA/xMyIE/IgDwhA/KEDMgTMiBPyIA8IQPyhAzIEzIgT8iAPCED8oQMyBMyIE/IgDwhA/KEDMgTMiBPyIA8IQPyhAzIEzIgT8iAPCED8oQMyBMyIE/IgDwhA/KEDMgTMiBPyIA8IQPyhAzIEzIgT8iAPCED8oQMyBMyIE/IgDwhA/KEDMgTMiBPyIA8IQPyhAzIEzIgT8iAPCED8oQMyBMyIE/IgDwhA/KEDMgTMiBPyIA8IQPyhAzIEzIgT8iAPCED8oQMyBMyIE/IgDwhA/KEDMgTMiBPyIA8IQPyhAzIEzIgT8iAPCED8oQMyBMyIE/IgDwhA/KEDMgTMiBPyIA8IQPyhAzIEzIgT8iAPCED8oQMyBMyIE/IgDwhA/KEDMi7AzLSZLNf8xCVAAAAAElFTkSuQmCC

is recognized by the Reporting engine as SVG, which results in the following error in the PictureBox:

An exception has occurred while processing 'pictureBox1' item:
System.Xml.XmlException: The '�' character, hexadecimal value 0xFFFD, cannot be included in a name. Line 1, position 5.
   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.ParseElement()
   at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
   at System.Xml.XmlDocument.Load(XmlReader reader)
   at System.Xml.XmlDocument.LoadXml(String xml)
   at Telerik.Reporting.Svg.RadSvgImage.SvgDocumentFromXml(String xml)
   at Telerik.Reporting.Processing.Imaging.SvgImageItem.CreateImageInfo()
   at Telerik.Reporting.Processing.Imaging.IImageInfoMapExtensions.StoreImageData(IImageInfoMap imageInfoMap, IImageItem imageItem, ICache cache)
   at Telerik.Reporting.Processing.PictureBox.ResolveImage(Object value)
   at Telerik.Reporting.Processing.PictureBox.ProcessItem()
   at Telerik.Reporting.Processing.ReportItemBase.ProcessElement()
   at Telerik.Reporting.Processing.ProcessingElement.Process(IDataMember dataContext)

Ideally, if the user prints a report, the output should be the same as what they see on the screen.

Currently, if the user prints/exports the report sometime after previewing it, the data will be updated and they will not get what they see.