Last Updated: 30 Sep 2022 06:34 by ADMIN

Enable retaining editable textboxes when Exporting to PDF.

For example a PDF Re-order form with editable textboxes for order Quantity so the user can enter order Quantities.

Pending Review
Last Updated: 29 Sep 2022 21:39 by Stephen McDaniel
Created by: Stephen McDaniel
Comments: 0
Type: Feature Request

Currently a single instance of the WPF Report Viewer will often use multiple different HttpClient instances to talk to the Report Server.  This means that cookies added as part of earlier requests may not be sent in later requests.  If the Report Server is behind a load balancer that uses cookies to implement 'sticky sessions', this loose behavior with cookies will cause requests to get routed to different servers which is not ideal.  It is possible to use a storage mechanism on the server that natively supports a web farm (such as the Redis storage option) but that can be tricky to set up.  

Instead, if the report viewer were to re-use the same HttpClient instance for all requests (including initial render request, export requests, print requests, etc.), the load balancer could work to route all requests to the same web server and then any storage mechanism (such as the simple File storage option) would work.

This issue was reported back in 2017 and I'm running into the problem again in 2022.  See: https://www.telerik.com/forums/wpf-reportviewer-cookie-behavior

Last Updated: 29 Sep 2022 14:43 by ADMIN
Created by: Chris Trina
Comments: 22
Type: Feature Request
Our clients enter information using the radeditor and in many cases want to embedded tables and graphics into their text.  Using your reporting tool there is no way to print this information.  I know you have suggested using your table and image tools, but that doesn't work when you are dealing with freely formatted text so the existance and location of the tables and images cannot be predicted.
Last Updated: 28 Sep 2022 11:58 by Thomas
Created by: Levi
Comments: 13
Type: Feature Request

What's the long-term plan for supporting Linux and Telerik Reporting? The dotnet design team is looking to remove support for System.Drawing.Common on Linux platforms. They're recommending compiler warnings in .Net 6, and full PlatformNotSupportedExceptions in .Net7



designs/system-drawing-win-only.md at main · dotnet/designs (github.com)

Breaking change: System.Drawing.Common only supported on Windows - .NET | Microsoft Docs

Last Updated: 27 Sep 2022 07:09 by ADMIN

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? 


Last Updated: 22 Sep 2022 06:20 by Tursunkhuja

Currently, the WinUI ReportViewer has a hard dependency on Windows due to the fact that the internals rely on the Win32 print dialog.

This means I cannot define the ReportViewer in a WinUI class library to be shared with multiple front-end WinUI projects. If you attempt to do this, there's an internal crash because the project cannot resolve  System.Windows.Forms.

This feature request is ask if you can replace the Win32 print dialog with the WinRT printing API. 


Research Note:  Here's a GitHub thread where Microsoft is discussing the topic Question: Printing in WinUI 3 Desktop · Issue #4419 · microsoft/microsoft-ui-xaml (github.com). Here's their current recommendation:

var hWnd = WinRT.Interop.WindowNative.GetWindowHandle(App.StartupWindow);
var printMan = PrintManagerInterop.GetForWindow(hWnd);

await PrintManagerInterop.ShowPrintUIForWindowAsync(hWnd)

In Development
Last Updated: 21 Sep 2022 14:24 by Yudiel
Scheduled for R3 2022

At the moment it's only possible to have your reports in old-fashioned projects.

It should be possible to add/design reports to SDK-style projects. That should work no matter what target framework is (.NET Core, .NET Standard or .NET Framework).

Last Updated: 21 Sep 2022 10:42 by ADMIN

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?

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.

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

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.

Last Updated: 15 Sep 2022 11:52 by ADMIN

Make the Design-Time parameter values of the WebServiceDataSource editable through code.

Currently, the design-time values can be edited only by the report designers or by saving the report with the TRDX extension and editing the XML.

In the XML, to change the design-time values, you may edit the ParameterValues property which is a string. 

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.


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


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.
Last Updated: 07 Sep 2022 12:29 by ADMIN
Created by: Tommy
Comments: 1
Type: Feature Request
Is it possible to re-oder parameters in the web designer?
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.




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.
Last Updated: 25 Aug 2022 13:14 by ADMIN
Currently, Telerik Report Designer cannot export the style heading level to the tag structure in the generated PDF. It exports the headings, yes, but only as a paragraph tag. This request would require that a Heading Level (e.g., Heading 1, Heading 2, Heading 3 ) field be added to the Properties panel such that a text box could be tagged as H1, H2, H3, etc.  According to accessibility guidelines, PDF/UA-1, WCAG 2.1 and 508, the tag tree needs to contain a logical reading order and tag structure. Heading Levels are essential to that. There may be only one H1 - usually reserved for the document title, then major sections get H2, subsections, H3, etc. Can this be done?
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?
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.
Last Updated: 23 Aug 2022 12:57 by ADMIN
I don't seem to be able to place an HTMLTextBox into a Table cell using the Web Designer... Is this not possible yet?
1 2 3 4 5 6