I have successfully installed the ODBC and OLEDB providers for Visual FoxPro 9 and they appear in the Windows 32-bit ODBC Data Sources under System DSN.
The drivers are discovered when I use Standalone Report Designer x86 from 17.2.23.1114 and older ones built against .NET Framework 4.0.
The same drivers are not found on the same machine when I use Standalone Report Designer x86 from 18.3.24.1218 built against .NET Framework 4.6.2.
I set globally the culture on the Linux Ubuntu Docker Container. Interestingly, the negative currency with en-US and fr-CA was displayed with the '-' sign rather than in brackets.
This was reproduced even in the values set with the Text Function FormatWithCulture(cultureName, format, args). The function displayed wrong formatting also on Windows, even in the Standalone Report Designer for .NET 8.
When the global culture on Windows was en-US, the negative decimal value formatted without the FormatWithCulture function was displayed correctly in .NET 8.
In the .NET Framework, the negative currencies were displayed as expected in all scenarios.
I have linked also a muted video showing the issue.
In the latest Reporting version, the interface of the report viewer allows users to set the value of a multiselect report parameter to an empty collection but not make it null.
In some scenarios, reports rely on parameters being null to filter their data and this makes them unusable in the latest version.
In Telerik Reporting versions before 18.1.24.514, I could change the order of items in a section by dragging an item up or down in the Report Explorer list.
If I try that now, nothing seems to happen on the screen. Dragging does not appear to change the position of an item in Report Explorer; the item appears to be fixed in place. However, if I close the report and reopen it, the position of the item may have changed.
The same happens if I use Send To Back/Brink to Front on an item. The new item position is not updated in the Report Explorer.
Password-protected PDF documents generated with Telerik Reporting have blank pages when opened with an iPhone.
After updating the Reporting version to v18, some error messages display the <br /> HTML element as text in the HTML5 Report Viewer. The issue was not present in v17.
Watermark Images with higher than the report rendering DPI are displayed clipped in PPTX rendering.
In PDF, preview of the designers and DOCX the same watermark is shown as expected.
If the DPI of the image is 96 as the default Windows machine DPI used for rendering, the Watermark is displayed correctly also in PPTX.
When I try to export a ReportBook to TIFF as explained in Exporting a report to a multi-document format, I receive an exception related to the file '.../report/image.tif' that cannot be created.
When I create the folder '.../report', there is another exception message:
'The process cannot access the file '...\report\image.tif' because it is being used by another process.'
The above error was thrown the second time the ReportProcessor tried to access the 'CreateStream' method from the code snippet in the above article. The 'image.tif' file is created and contains only the first report from the ReportBook.
With version 15.0.21.112 the last exception is not thrown and the 'image.tif' file contains all reports from the ReportBook.
When the reporting service fails to generate a report document, the Get Document Info request returns a 500 response with the error message thrown from within the reporting engine. However, instead of displaying the error message in the viewport, the Native Blazor Report Viewer displays a message falsely suggesting that the report is still being rendered when the rendering has, in fact, failed.
2. Toolbar Button Properties: Along with this, since IReportViewerTool exposes the Icon and CommandName, request it also expose an Enabled property. At a bare minimum, it would be helpful if, while rendering, all but the 'Stop Rendering' (Cancel) and Pager buttons are disabled by default or by setting a new viewer property.
Currently we must use JSInterop to accomplish these things.
The reason we are managing these things in the first place is because we are using Custom Parameter Editors (CPEs). When a long-running report is in the process of rendering, and a user changes a parameter and re-requests the report (either via our 'Retrieve' button or a viewer toolbar button), an unhandled exception occurs in _content/Telerik.ReportViewer.BlazorNative/js/reporting-blazor-viewer.js. So we make use of the OnRenderingBegin and OnRenderingEnd events to disable/enable the CPEs. The problem arises when the 'Stop Rendering' (Cancel) button is clicked. Since we cannot detect the button click, our CPEs remain disabled.
Currently, the Native Angular Report Viewer does not support NodeJS 22. It is restricted to v16-21 of NodeJS and I would have to downgrade to use it.
I have created an abstract class in my report library that inherits from Telerik.Reporting.Report. When I try to load the project's assembly in the Standalone Report Designer to import those reports as TRDP, an exception is thrown while the application tries to load the assembly that there are report types that do not have a parameterless constructor.
To resolve the issue, I had to remove the 'abstract' modifier. However, that should not be necessary. The wizard should ignore abstract classes or at the very least, let me import the other report types while displaying a message that there are report types with parameterless constructors.
When trying to open reports from an assembly in the Standalone Report Designer so that they can be imported, if there are types that inherit from Telerik.Reporting.Report that do not have a parameterless constructor, this will cause an exception as it is required for the report types to have such a constructor, otherwise, the wizard cannot import them into TRDP.
In this scenario, the report types that do not have a parameterless constructor should be written to the trace or in the exception message dialog so that the user can see which are the problematic types and correct them.
Images taken with a mobile device are sometimes displayed in PictureBox rotated by 90, 180 or 270 degrees. The reason is that whenever a photo is taken, the device saves its current accelerometer orientation into a corresponding Exif tag with the image metadata, so this info is then read and taken into account by our Report Designer.
In the standalone designer, it would be helpful if you could drag and drop the column headers to reorder. At present you have to add a new column and delete the old one, remembering to copy all properties.
We have reports that contain a table of images. This seems to work great in the designer and when generated to a PDF without accessibility turned on. However, with accessibility turned on and rendering to a PDF, it throws an exception:
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.InitTaggedElement(AccessibilityPdfElement pdfElementType)
at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.AddFigureElement(ITableCell element)
at Telerik.Reporting.Processing.ProcessingElementVisitor.Visit(LayoutElement element)
at Telerik.Reporting.Writing.AccessibilityElementWriter.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.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.WriteOperationsDispatcher.Visit(PictureBox pictureBox)
at Telerik.Reporting.Processing.ProcessingElementVisitor.Visit(LayoutElement element)
at Telerik.Reporting.Writing.DocumentWriter.Telerik.Reporting.BaseRendering.IWriter.WriteStartElement(LayoutElement element, ElementPageInfo pageInfo)
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 the attached report, all items in the detail section have Docking set to Top.
In the Interactive view of the report designer, the report looks fine.
In PrintPreview mode though, some items overlap.