Completed
Last Updated: 20 Nov 2024 16:09 by ADMIN
Release 2024 Q4
Currently, there is no natural way to disable picturebox errors. Sometimes we do not care to know that the image wasn't found, especially when the error shown severely damages the look of the report, stretching and pushing things out of the way. The image URL may be built via parameters, pointing to a large folder where photos of a given employee may or may not exist. It took multiple unhelpful support tickets, many headaches and days of research to finally find an obscure post by a private individual with an undocumented custom solution that worked. 
Completed
Last Updated: 14 Nov 2024 11:02 by ADMIN
Release 2024 Q4

The Uri user function can be selected from the functions list in the expression editor of the designer but when the report is previewed the following error message is shown.

The expression contains undefined function call Uri()

Completed
Last Updated: 14 Nov 2024 11:02 by ADMIN
Release 2024 Q4

Just a simple quality-of-life improvement, middle-click on the tab should close the report - doing exactly the same thing as clicking the "X" button in the tab. Seems the majority of tabbed UIs follow this convention.

Completed
Last Updated: 14 Nov 2024 11:02 by ADMIN
Release 2024 Q4

We have an app that loads a list of reports. When a report is selected, a report viewer page is loaded. It contains a set of parameters. In this stage, we get a http 400 error because it is the hitting the GetParameters endpoint right away. The user has not selected any parameters. It should only hit this endpoint when the user has selected the parameters and runs the report.

This is not the behavior in the HTML viewer.

In the images attached, the Initial Load image is the error we get when the report viewer page is loaded.
The Report Source is the payload when the GetParameters endpoint is called. As you can see it's empty since the report is not ran yet.
In the Running image, the error is when the user runs the report.

Completed
Last Updated: 07 Aug 2024 10:27 by ADMIN
Release 2024 Q3
Created by: Lars Rikard
Comments: 0
Type: Feature Request
1

The WPF Report Viewer should support rounded corners.

Currently, I am not allowed to do the following:

<telerikReport:ReportViewer Grid.Row="1"
                            Grid.Column="1" 
                            Name="reportViewer1"
                            ReportSource="{Binding ReportSource}">
    <telerikReport:ReportViewer.Resources>
        <Style TargetType="telerikReport:ReportViewer" BasedOn="{StaticResource {x:Type telerikReport:ReportViewer}}">
            <Setter Property="BorderBrush" Value="{telerik:Windows11Resource ResourceKey=PrimaryBorderBrush}"/>
            <Setter Property="BorderThickness" Value="1"/>
            <Setter Property="Margin" Value="5"/>
            <Setter Property="CornerRadius" Value="4"/>
        </Style>
    </telerikReport:ReportViewer.Resources>
</telerikReport:ReportViewer>

Completed
Last Updated: 07 Aug 2024 10:27 by ADMIN
Will it be possible to configure the stand-alone report designer to use the Skiasharp rendering engine when generating export files from the preview? This would help us verify that what we see at design-time is similar to what is being generated at run-time. Currently we have to copy report files into a Linux docker container to perform this type of testing.
Completed
Last Updated: 03 Jun 2024 10:40 by ADMIN
Release 2024 Q3

Hello,

We would like to know if/and when Query Designer will be implemented in web report designer?

Completed
Last Updated: 06 Feb 2024 08:19 by ADMIN

In Web Report Designer HtmlTextBox input is just simple TextArea. There is a great need to be able to enter rich text as in a desktop application.

https://docs.telerik.com/reporting/report-items/htmltextbox/overview

Completed
Last Updated: 31 Jan 2024 17:59 by ADMIN
Release 2024 Q1

I have a following default code in a html file for a web designer.

$(document).ready(function () {
            $("#webReportDesigner").telerik_WebReportDesigner({
                persistSession: false,
                toolboxArea: {
                    layout: "list"
                },
                serviceUrl: "some url",
                report: "some_report_name",
            }).data("telerik_WebDesigner");
        });

I have also a custom report storage implemented from IDefinitionStorage, where I have a GetDefinition("some_report_name") method implemented in a custom way. In order to do that, I need to send additional parameters from a web designer (html code provided previously) but don't know how to do that. 

For example, I need to open SalesInvoice.trdx file and I do a following: report: "SalesInvoice.trdx". If i need to send additional parameter, let's say some kind of token, there is no good place to send it. As a work around, i am doing report: "SalesInvoice.trdx&token=123". The problem with this, it is appearing in a title of a web designer and I don't want that. In an attachments, there is a screenshot where it looks good with a simple name and the one which has a token in it.

So, the question is, can I send other parameters as well from a client side of web designer to the server like parameters or so?

In a HTML5 ReportViewer we can send report file name and parameters as a reportSource like this:

                    serviceUrl: serviceUrl,
                    reportSource: {
                        report: reportUrl,
                        parameters: reportParams,

Can we do the same? Or how can I do that?

Completed
Last Updated: 31 Jan 2024 17:38 by ADMIN
Release 2024 R1 PI1
Created by: Levi
Comments: 71
Type: Feature Request
54

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

 

Sources:

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

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

Completed
Last Updated: 31 Jan 2024 15:12 by ADMIN
Release 2024 Q1
Created by: Tursunkhuja
Comments: 11
Type: Feature Request
16

Hello,

We use WebServiceDataSource with OData query in our reports. Sometimes OData can through an exception.

In our case, we have added Web Service DataSource and set this OData query for its Service Url:

https://services.odata.org/V3/Northwind/Northwind.svc/Products(1)?$select=ProductName1

If you see the query, it is selecting "ProductName1" property of "Product #1". But "ProductName1" property does not exist (correct property name is "ProductName"). When we use Postman for the OData query above, it shows an error which you can see from attached picture (ErrorWhenWeUsePostman.PNG, "Could not find a property named 'ProductName1' on type 'NorthwindModel.Product'"). From the second picture (TelerikReportingGeneralError.PNG, "An error has occurred... Response status code does not indicate success: 400 (Bad Request).") you can see the result of our test report (in html5 report viewer) that has the same OData query.

The question is when we preview our report (in html5 report viewer) how can we show the error message that OData sent instead of showing Telerik reporting general error?
Instead of this message:

An error has occurred while processing Report 'TestReportWithWebServiceDataSource': Response status code does not indicate success: 400 (Bad Request).

This OData error message should be handled and shown on browser (html5 report viewer) when previewing report:

Could not find a property named 'ProductName1' on type 'NorthwindModel.Product'

FYI: We are using Telerik Reporting version 15.0.21.224.

This is my post on Telerik forum related with this: How to get internal error message from Custom Report Resolver

Thank you,

Completed
Last Updated: 31 Jan 2024 12:24 by ADMIN
Release 2024 Q1

In .NET Core the localization routines have changed and the approach to localize an application provided in the documentation doesn't work.

When adding the localized .resx files as described in the documentation - with BuildAction set to None - the resource strings cannot be obtained and even the default string values are lost. This effect can be mitigated with changing the BuildAction to EmbeddedResource.

 

Completed
Last Updated: 31 Jan 2024 11:11 by ADMIN
Release 2024 Q1

In the Desktop Report Designers, you may display the Text of the Tooltips on several lines by adding new lines (\n) inside the text.

In the HTML5 Viewrs, the new lines are ignored and the text is displayed on a single line. You may work around this by replacing the new lines with <br /> elements. It would be much easier for the users if this is done in the code of the viewer instead.

Completed
Last Updated: 31 Jan 2024 11:11 by ADMIN
Release 2024 Q1
It would be extremely useful to be able to show descriptions for individual properties of designer and, of course, to display them translated.

In desktop app we have some space with description


In web designer it would be nice to show some info in tooltip or another way like you prefer

Completed
Last Updated: 23 Jan 2024 06:57 by ADMIN
Release 2024 Q1

The OpenXML renderings in .NET work with DocumentFormat.OpenXml 2.7.2 - 2.20.0

When upgrading to version 3.0.0 the Word rendering throws the following exception:

CSharp.Net7.Html5IntegrationDemo Error: 0 : System.TypeInitializationException: The type initializer for 'Telerik.Reporting.OpenXmlRendering.Wordprocessing.DocumentHelper' threw an exception.
 ---> System.TypeLoadException: Could not load type 'DocumentFormat.OpenXml.Packaging.ImagePartType' from assembly 'Telerik.Reporting.OpenXmlRendering.2.7.2, Version=17.2.23.1114, Culture=neutral, PublicKeyToken=a9d7983dfcc261be' due to value type mismatch.
   at Telerik.Reporting.OpenXmlRendering.Wordprocessing.DocumentHelper..cctor()
   --- End of inner exception stack trace ---
   at Telerik.Reporting.OpenXmlRendering.Wordprocessing.DocumentHelper.CreateMainPart(WordprocessingDocument package)
   at Telerik.Reporting.OpenXmlRendering.Wordprocessing.DocumentBuilder.CreateMainPart()
   at Telerik.Reporting.OpenXmlRendering.Wordprocessing.DocumentBuilder.CreateBodyLayout()
   at Telerik.Reporting.OpenXmlRendering.Wordprocessing.ReportWriter.WriteDocument(DocumentBuilder documentBuilder, LayoutElement layoutElement)
   at Telerik.Reporting.OpenXmlRendering.Wordprocessing.WordprocessingWriter.WriteEndElement(LayoutElement source, ElementPageInfo pageInfo)
   at Telerik.Reporting.BaseRendering.PageHandler.Telerik.Reporting.Paging.IPageHandler.EndElement(LayoutElement element, ElementPageInfo info)
   at Telerik.Reporting.Paging.PageEndElement.OutputToPage(IPageHandler handler)
   at Telerik.Reporting.Paging.PageElementsLayer.OutputToPage(IPageHandler handler)
   at Telerik.Reporting.Paging.PageContent.Output(IPageHandler handler)
   at Telerik.Reporting.Paging.PageCompositionBase.OutputPageContent(Stopwatch stopwatchOutputContent, PageContent pageContent)
   at Telerik.Reporting.Paging.PageCompositionBase.<>c__DisplayClass124_0.<CreatePageContentOutputTask>b__0()
An error has occurred while rendering the report: System.OperationCanceledException: The operation was canceled.
   at System.Threading.CancellationToken.ThrowOperationCanceledException()
   at System.Threading.ManualResetEventSlim.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.SpinThenBlockingWait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.InternalWaitCore(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.Wait(CancellationToken cancellationToken)
   at Telerik.Reporting.Paging.PageCompositionBase.SeparateThreadOutputBehavior.Finish()
   at Telerik.Reporting.Paging.PageCompositionBase.CreatePages()
   at Telerik.Reporting.Paging.PagerBase.Telerik.Reporting.Paging.IPager.CreatePages(IPageHandler handler, LayoutElement root)
   at Telerik.Reporting.BaseRendering.RenderingExtensionBase.Render(LayoutElement root, Hashtable renderingContext, Hashtable deviceInfo, CreateStream createStreamCallback, EvaluateHeaderFooterExpressions evalHeaderFooterCallback, PageSettings pageSettings)
*** Render Report #0 "ReportCatalog" DONE in 00:00:00.2183346 ***

CSharp.Net7.Html5IntegrationDemo Error: 0 : An error occurred while rendering the report in separate thread: System.OperationCanceledException: The operation was canceled.
   at System.Threading.CancellationToken.ThrowOperationCanceledException()
   at System.Threading.ManualResetEventSlim.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.SpinThenBlockingWait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.InternalWaitCore(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.Wait(CancellationToken cancellationToken)
   at Telerik.Reporting.Paging.PageCompositionBase.SeparateThreadOutputBehavior.Finish()
   at Telerik.Reporting.Paging.PageCompositionBase.CreatePages()
   at Telerik.Reporting.Paging.PagerBase.Telerik.Reporting.Paging.IPager.CreatePages(IPageHandler handler, LayoutElement root)
   at Telerik.Reporting.BaseRendering.RenderingExtensionBase.Render(LayoutElement root, Hashtable renderingContext, Hashtable deviceInfo, CreateStream createStreamCallback, EvaluateHeaderFooterExpressions evalHeaderFooterCallback, PageSettings pageSettings)
   at Telerik.Reporting.BaseRendering.RenderingExtensionBase.Render(Report report, Hashtable renderingContext, Hashtable deviceInfo, CreateStream createStreamCallback, EvaluateHeaderFooterExpressions evalHeaderFooterCallback)
   at Telerik.Reporting.Processing.ReportProcessor.RenderCore(ExtensionInfo extensionInfo, IList`1 processingReports, Hashtable deviceInfo, IRenderingContext renderingContext, CreateStream createStreamCallback)
   at Telerik.Reporting.Processing.ReportProcessor.RenderCore(String format, IList`1 reports, Hashtable deviceInfo, IRenderingContext renderingContext, CreateStream createStreamCallback)
   at Telerik.Reporting.Services.Engine.ReportRenderer.Render(ReportRendererArgs args)
   at Telerik.Reporting.Services.Engine.Rendering.RenderWithCulture(ReportRendererArgs args)
   at Telerik.Reporting.Services.Engine.Rendering.ThreadFunc(Object o)

 

I would prefer my OpenXML rendering to work with the latest DocumentFormat.OpenXml version.

Completed
Last Updated: 18 Jan 2024 16:40 by ADMIN
Created by: Peter
Comments: 4
Type: Feature Request
28
Optimize the Telerik Reporting performance by parallelizing the reporting paging and rendering. Better utilize CPUs with multiple cores and as a result, improve the REST Service throughput and decrease the viewers' rendering times.
Completed
Last Updated: 18 Jan 2024 08:56 by ADMIN
Release 2023 R3
Created by: Todor
Comments: 8
Type: Feature Request
41

The Web Report Designer's current layout is not flexible and cannot be customized. It will be useful to allow changes in the designer template, styles, etc.

For example, in some scenarios, the users should not be allowed to add DataSources to the report. In this case, the DataSources components should be hidden or disabled, which currently can be achieved with custom jQuery code.

In other scenarios, it may be necessary to change the styles of the designer elements.

It will be useful for the designer to expose also events.

Completed
Last Updated: 07 Dec 2023 09:22 by ADMIN
Release 2024 R1 PI1
Export the images to Word with the new "graphic" and "pic" tags instead of the VML tags.  The VML is an obsoleted feature no longer used nad such shapes cannot be properly edited in Word. In addition the WPF and Winforms RadRichTextBox do not support them as well. 
Completed
Last Updated: 15 Nov 2023 17:17 by ADMIN
Release 2024 R1 PI1
Currently, in the Web Report designer, when you define a Binding, there is no dropdown with the available property paths as it is in the desktop designers.
Completed
Last Updated: 06 Nov 2023 15:42 by ADMIN
Release R2 2019 SP1
With the recent release of StackExchange.Redis v2.0 there are HARD BREAK changes. I would like Telerik Reporting to work also with this version.
1 2 3 4 5 6