Declined
Last Updated: 27 Sep 2022 07:09 by ADMIN
Created by: Tursunkhuja
Comments: 6
Category: Reporting
Type: Feature Request
4

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.  

Graphical user interface, text, application, email

Description automatically generated

Is it on your roadmap to implement that feature? 

Thanks,

Under Review
Last Updated: 26 Sep 2022 09:37 by ADMIN
Created by: Evgenii
Comments: 3
Category: Reporting
Type: Bug Report
0

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?

Unplanned
Last Updated: 23 Sep 2022 07:11 by Todor

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.

Unplanned
Last Updated: 21 Sep 2022 13:35 by Steve
When you exporting the template from a report on the report server, it gives the "Template build failed" error message.
Unplanned
Last Updated: 21 Sep 2022 10:42 by ADMIN
Created by: Peter
Comments: 1
Category: Reporting
Type: Feature Request
1

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?

Completed
Last Updated: 21 Sep 2022 06:19 by ADMIN

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.

Completed
Last Updated: 19 Sep 2022 09:42 by ADMIN
Created by: Franz
Comments: 8
Category: Reporting
Type: Feature Request
14

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.

Unplanned
Last Updated: 16 Sep 2022 13:32 by Anthony

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.

Completed
Last Updated: 14 Sep 2022 14:34 by James
Release R3 2022

Steps to reproduce the problem:

1. Open the attached report in EUD
2. Ensure its RuntimeSettings contain parameter "EnableAccessibility" set to True or add the setting before opening the designer in its configuration file
3. Preview the report and export it to PDF


EXPECTED:
The produced PDF is tagged (accessible) - check it in Acrobat Reader's file properties in the bottom left corner. The file size should be ~155KB
OBSERVED:
The produced PDF is not tagged (accessible). Its size is ~123KB.
Completed
Last Updated: 14 Sep 2022 14:06 by ADMIN
Release R3 2022

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.

Unplanned
Last Updated: 14 Sep 2022 08:19 by Bart

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)

Unplanned
Last Updated: 08 Sep 2022 10:17 by Jason

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.

Unplanned
Last Updated: 07 Sep 2022 13:17 by ADMIN

When exporting to PDF from Telerik Report Designer the software creates a list of flat links for each TOC entry, but the links are separated in the structure from the TOC Label. While a good start, it would be better to use a main TOC tag under which each line in the TOC would receive a TOCI (Table of Contents Item) tag. Each TOCI would contain the label and link for the respective item. Attaching a few examples to assist.

<TOC> Table of contents element is an element that contains a structured list of items and labels identifying those items; has its own discrete hierarchy.
<TOCI> Table of contents item element is an item contained in a list associated with a table of contents element.

References:

https://www.hhs.gov/sites/default/files/pdf-tagging.pdf (page 29).

https://www.pdflib.com/pdf-knowledge-base/pdfua/the-pdfua-standard/ 

Unplanned
Last Updated: 07 Sep 2022 12:33 by ADMIN
When exporting to PDF from Telerik Report Designer, single fields of information are broken out into separate tags (by line) rather than lumped into one tag. If possible, it would be better to have all data from the field sent to one Paragraph tag to facilitate reading via accessibility reading technology.
Declined
Last Updated: 05 Sep 2022 14:35 by StillLearnin

Clicking the cancel button on the HTML5 report viewer show "Report processing was canceled" in the UI but the report is still being generated and rendered on the server.

In this old thread it is stated that it isn't possible to cancel the report generation on the server. Is that still the case?

Unplanned
Last Updated: 01 Sep 2022 12:10 by Satya
Some horizontal page breaks force report processing to create an invalid page clipping during paging. 

In my report, when the content fits in the page width, the PDF document is generated correctly. When there is a horizontal page break though, the content of the pages after the first one is clipped.
Unplanned
Last Updated: 30 Aug 2022 10:14 by ADMIN

When exporting the tags for the document's Table of Contents Telerik Report Designer exports TOC leaders as distinct tags, requiring that they be removed when completing the accessibility tagging for the document. Leaders - the ellipses found in the Table of Contents (e.g., Introduction ...................... Page 3) between the TOC item and the page number will be read by assistive technology as "dot dot dot dot dot..." etc. They need to be deleted from the tag tree. Please Artifact them or (preferably) NOT tag them on the export. Thanks.

Reference: 

https://www.levelaccess.com/pdf-table-of-contents/

https://www.w3.org/TR/2014/NOTE-WCAG20-TECHS-20140408/pdf.html 

Declined
Last Updated: 29 Aug 2022 18:54 by James
Many documents have repeating information that is irrelevant and needs to be untagged, or artifacted, so that assisstive technology does not share the information multiple times. Common examples of this situation are headers, footers, page numbers, and decorative images. In most cases, it is not necessary to read these document elements on each page, so we untag the information to prevent repetition for the person reading the document with assistive technology. Is there a way to mark a report section - e.g., the page header or page footer - as Untagged or Artifacted, and have those tags be exported to the PDF? It would save a ton of time having to manually go through several hundred pages and untagging them manually.
Declined
Last Updated: 25 Aug 2022 12:07 by James
Telerik Report Designer is one of the few report writing tools on the market that can export tagged PDF content. It's a major advantage of your solution. Why can it not be turned on by default, or enabled via a menu button. Better yet, how about including an Accessibility menu setting to allow for more detailed configuration of key elements?
Unplanned
Last Updated: 25 Aug 2022 12:01 by James
I produce a lot of Accessible PDF documents that include many unique images - hundreds in most cases. Each image has alt text descriptions in it in the EXIF metadata of the image file itself. Most of the documents I generate a based on a one or two page template used for each record ID. The images are loaded programmatically based on the ID number for the template. Right now, with Accessibility Enabled, Telerik cannot read the image EXIF data. It would be ideal if it could be configured to pick up the descriptions already inside the image file itself. This applies to the stand alone Report Designer and the Visual Studio version.