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.
If I create a report with a report parameter whose value is initially False, and then load it in the Native Angular Report Viewer, it is initially loaded properly.
However, if I click the "Preview" button, and the parameter is still unchecked(false), I get an error that the value is invalid.
The issue does not reproduce if the report parameter has AutoRefresh=True and there is no "Preview" button. I can successfully change the value of the parameter and the report loads without errors.
The following exception is thrown when rendering a report with enabled Accessibility to PDF with Skia if the report has a Table containing an HtmlTextBox:
Telerik.ReportDesigner.Net Error: 0 : System.NullReferenceException: Object reference not set to an instance of an object.
at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.TryAttachToParentNode(ProcessingInstanceIdentifier id, PdfOrderedReference element, Int32 rowIndex, Int32 columnIndex)
at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.TryAttachToParentNode(IProcessingElement processingElement, IProcessingElement parentProcessingElement, PdfOrderedReference taggedElementReference)
at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.AttachNonLeafNode(LayoutElement element, PdfOrderedReference taggedElementReference)
at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.AttachNodeToTree(AccessibilityPdfElement pdfElementType, PdfOrderedReference taggedObjectReference)
at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.InitTaggedElement(AccessibilityPdfElement pdfElementType)
at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.AddParagraphElement(ITableCell element)
at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.Visit(HtmlTextBox htmlTextBox)
at Telerik.Reporting.Processing.HtmlTextBox.Accept(ProcessingElementVisitor visitor)
at Telerik.Reporting.Processing.ProcessingElementVisitor.Visit(LayoutElement element)
at Telerik.Reporting.Writing.AccessibilityElementWriter.StartWrite(ReportItemBase element, Int32& index)
at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.StartWrite(ReportItemBase element, Int32& index)
at Telerik.Reporting.Writing.VisualElementWriter`1.StartWriteAccessibilityItem(ReportItemBase item, ElementPageInfo pageInfo, DocumentWriter writer)
at Telerik.Reporting.Writing.VisualElementWriter`1.WriteClientFocusableItems(T element, ElementPageInfo pageInfo, DocumentWriter writer)
at Telerik.Reporting.Writing.VisualElementWriter`1.StartWrite(T element, ElementPageInfo pageInfo, DocumentWriter writer)
at Telerik.Reporting.Writing.ReportItemBaseWriter`1.StartWrite(T element, ElementPageInfo pageInfo, DocumentWriter writer)
at Telerik.Reporting.Writing.ElementWriter`1.Telerik.Reporting.Writing.IElementWriter.StartWrite(LayoutElement element, ElementPageInfo pageInfo, DocumentWriter writer)
at Telerik.Reporting.Writing.WriteStartOperationsDispatcher.Write(IElementWriter writer, LayoutElement element, ElementPageInfo pageInfo, DocumentWriter documentWriter)
at Telerik.Reporting.Writing.WriteOperationsDispatcher.Write(IElementWriter writer, LayoutElement element)
at Telerik.Reporting.Writing.WriteOperationsDispatcher.Visit(HtmlTextBox htmlTextBox)
at Telerik.Reporting.Processing.HtmlTextBox.Accept(ProcessingElementVisitor visitor)
at Telerik.Reporting.Processing.ProcessingElementVisitor.Visit(LayoutElement element)
at Telerik.Reporting.Writing.WriteOperationsDispatcher.DispatchWriteOperation(LayoutElement element, ElementPageInfo pageInfo)
at Telerik.Reporting.Writing.DocumentWriter.Telerik.Reporting.BaseRendering.IWriter.WriteStartElement(LayoutElement element, ElementPageInfo pageInfo)
at Telerik.Reporting.BaseRendering.PageHandler.Telerik.Reporting.Paging.IPageHandler.StartElement(LayoutElement element, ElementPageInfo info)
at Telerik.Reporting.Paging.PageStartElement.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()
Telerik.ReportDesigner.Net Error: 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)A similar error is thrown when rendering with GDI+.
Currently, you can select multiple report items with the CTRL when you run the Web Report Designer on Mac, however, this is interpreted as a right-click. Please, check the attached video.
The correct behavior should be by using CMD.
Hi,
HTML viewer is showing Arabic words correctly while PDF Export shows splitted characters.
Correct word : فاتورة
Wrong word with splitted characters : ةروتاف
Please find attached screenshots for reference. The issue is appearing only with Linux container.
Telerik support ticket (https://www.telerik.com/account/support-center/view-ticket/1623687) was created and got reply that it is because of libgdiplus library and we were expecting that this issue will be resolved in R2 2023 but it still persists.
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()
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.
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.
I have a report that uses custom assemblies and I export it through the ReportProcessor class in my .NET application.
For the reporting engine to resolve the custom assemblies, I had to pass an IConfiguration instance through its constructor where the custom assembly is referenced in the assemblyReferences element - Configuration for the ReportProcessor in .NET.
This approach does not work with the latest version of Telerik Reporting(18.2.24.924). I get errors that the assembly and the used types are not registered in the configuration file when I render the report.
According to the HTML5 Report Viewer documentation, the persistSession property of the viewer should be set to false by default.
This is not the case for the HTML5 WebForms Report Viewer, the value of its PersistSession property is true by default.
Since the HTML5 WebForms Report Viewer is a wrapper of the HTML5 Report Viewer, it should have the same default values.
Using the MySQL Connector/NET data provider with the latest version of Telerik Reporting - Telerik Reporting - Progress® Telerik® Reporting 2024 Q3 (18.2.24.924), leads to the following error when using Stored Procedures:
System.ArgumentException: Object of type 'MySql.Data.MySqlClient.MySqlCommand' cannot be converted to type 'System.Data.SqlClient.SqlCommand'.
at System.RuntimeType.TryChangeType(Object value, Binder binder, CultureInfo culture, Boolean needsSpecialCast)
at System.Reflection.MethodBase.CheckArguments(Object[] parameters, Binder binder, BindingFlags invokeAttr, CultureInfo culture, Signature sig)
at System.Reflection.RuntimeMethodInfo.InvokeArgumentsCheck(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at Telerik.Reporting.Processing.Data.SqlProviderFactory.DeriveParameters(IDbCommand command)
at Telerik.Reporting.Processing.Data.SqlCommandProvider.ResolveProcedure(IDbCommand command, SqlDataSourceParameterCollection parameters)
at Telerik.Reporting.Processing.Data.SqlQueryProvider.CreateCommandCore(IDbConnection connection, Boolean evaluateParameters)
at Telerik.Reporting.Processing.Data.SqlQueryProvider.CreateCommand(IDbConnection connection)
at Telerik.Reporting.Processing.Data.SqlDataEnumerable.<GetEnumerator>d__2.MoveNext()
at Telerik.Reporting.Processing.Data.LazyList`1.LazyListEnumerator.MoveNext()
at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
at Telerik.Reporting.Processing.Data.SeedDataAdapter.Execute(IEnumerable`1 data)
at Telerik.Reporting.Processing.Data.ResultSetAdapter.Execute(IEnumerable`1 data)
at Telerik.Reporting.Processing.Data.MultidimentionalDataProvider.Execute(MultidimensionalQuery query)
at Telerik.Reporting.Processing.DataItemResolveDataAlgorithm.GetDataCore(IDataSource dataSource, MultidimensionalQuery query, IServiceProvider serviceProvider, EvalObject expressionContext, IProcessingContext processingContext)
at Telerik.Reporting.Processing.Report.GetDataCore(IDataSource dataSource, MultidimensionalQuery query)
at Telerik.Reporting.Processing.DataItemResolveDataAlgorithm.ResolveData(String processingId, InMemoryState inMemoryState, MultidimensionalQuery query, Func`1 getDataCore, EvalObject expressionContext)
at Telerik.Reporting.Processing.Report.ResolveData()
at Telerik.Reporting.Processing.Report.ProcessItemCore()
at Telerik.Reporting.Processing.Report.ProcessItem()
at Telerik.Reporting.Processing.ReportItemBase.ProcessElement()
at Telerik.Reporting.Processing.ProcessingElement.Process(IDataMember dataContext)The previous version - Telerik Reporting - Progress® Telerik® Reporting 2024 Q3 (18.2.24.806), is working fine.
When rendering a report to PDF with the accessibility feature enabled - PDF Device Information Settings at a glance - Telerik Reporting, if there is a table/list/crosstab item that contains an item with a Navigate To Bookmark action pointing to the same BookmarkId, the document won't be rendered because of the following error:
System.ArgumentException: An item with the same key has already been added. Key: (table1) Table X=3810 Y=762 Width=2990 Height=1830
at System.Collections.Generic.Dictionary`2.TryInsert(TKey key, TValue value, InsertionBehavior behavior)
at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.Visit(Table table)
at Telerik.Reporting.Processing.Table.Accept(ProcessingElementVisitor visitor)
at Telerik.Reporting.Processing.ProcessingElementVisitor.Visit(LayoutElement element)
at Telerik.Reporting.Writing.AccessibilityElementWriter.StartWrite(ReportItemBase element, Int32& index)
at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.StartWrite(ReportItemBase element, Int32& index)
at Telerik.Reporting.Writing.VisualElementWriter`1.StartWriteAccessibilityItem(ReportItemBase item, ElementPageInfo pageInfo, DocumentWriter writer)
at Telerik.Reporting.Writing.VisualElementWriter`1.WriteClientFocusableItems(T element, ElementPageInfo pageInfo, DocumentWriter writer)
at Telerik.Reporting.Writing.VisualElementWriter`1.StartWrite(T element, ElementPageInfo pageInfo, DocumentWriter writer)
at Telerik.Reporting.Writing.ReportItemBaseWriter`1.StartWrite(T element, ElementPageInfo pageInfo, DocumentWriter writer)
at Telerik.Reporting.Writing.ElementWriter`1.Telerik.Reporting.Writing.IElementWriter.StartWrite(LayoutElement element, ElementPageInfo pageInfo, DocumentWriter writer)
at Telerik.Reporting.Writing.WriteStartOperationsDispatcher.Write(IElementWriter writer, LayoutElement element, ElementPageInfo pageInfo, DocumentWriter documentWriter)
at Telerik.Reporting.Writing.WriteOperationsDispatcher.Write(IElementWriter writer, LayoutElement element)
at Telerik.Reporting.Writing.WriteOperationsDispatcher.Visit(Table table)
at Telerik.Reporting.Processing.Table.Accept(ProcessingElementVisitor visitor)
at Telerik.Reporting.Processing.ProcessingElementVisitor.Visit(LayoutElement element)
at Telerik.Reporting.Writing.WriteOperationsDispatcher.DispatchWriteOperation(LayoutElement element, ElementPageInfo pageInfo)
at Telerik.Reporting.Writing.DocumentWriter.Telerik.Reporting.BaseRendering.IWriter.WriteStartElement(LayoutElement element, ElementPageInfo pageInfo)
at Telerik.Reporting.BaseRendering.PageHandler.Telerik.Reporting.Paging.IPageHandler.StartElement(LayoutElement element, ElementPageInfo info)
at Telerik.Reporting.Paging.PageStartElement.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()
In my report, I show a tiny goat symbol with the font 'Segoe UI Emoji'. It looks good in the Standalone Designer for .NET Framework, but it is not shown in the PDF export from my .NET application, although the font is correctly embedded.
In the Standalone Report Designer for .NET 8, the goat is not displayed when previewing or exporting either.
The Editor-Control for the HTMLTextBox does not use the localized values from the WebReportDesignerStrings.xx.js.
Some SVG files are not rendered as expected when the PDF Rendering is used.
SVG opened in the browser:
SVG in rendered PDF file:
When the latest Kendo UI version is used, the ellipsis in the Web Report Designer's Report Explorer tree are invisible, and the context menus of some report items cannot be opened.
For example, adding shared data sources to a report is not possible because this functionality is accessible through the context menu of the [Shared Data Sources] collection in the explorer tree.
Expected behavior:
Actual behavior:
To work around the issue, use the 2022.3.913 Kendo UI version on the Web Report Designer page.
When I enable accessibility in the Angular Report Viewer, based on the HTML5 Report Viewer, I get the following console error:
Uncaught TypeError: Cannot read properties of undefined (reading '_controller')
at telerikReportViewer:1:15863
at Ce. (telerikReportViewer:1:16167)
at Ce.n (telerikReportViewer:1:26372)
at Ce.trigger (telerikReportViewer:1:26686)
at ce (telerikReportViewer:1:32782)
at Object.updateUI (telerikReportViewer:1:43789)
at telerikReportViewer:1:93236The report viewer continues being functional despite the error but accessibility text is missing for page number, export, and buttons(incl. parameters area).
The getReportParameters method of the HTML5 Report Viewer omits parameters with unset values that have their AllowNull property set to False.
The reportSource method of the HTML5 Report Viewer can be used as an alternative.