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.
All of my report parameters have their AutoRefresh setting set to False, and the parameters do not depend on each other, they are not cascading parameters. The parameters have available values.
If I change the value of one of the parameters, despite the above settings, all of the other parameters' data is re-retrieved(even if those parameters are not visible).
This causes issues because the "Preview" button is disabled until the parameters are refreshed, and makes the UX bad since if the connection is slow, the end-users will have to wait for the parameters area to refresh after changing any parameter value.
DPI Awareness Settings are not applied when printing from the ReportProcessor in .NET where the configuration is provided in the constructor.
However, if I manually invoke the SetProcessDpiAwareness function before triggering the printing, the DPI is successfully updated.
Just like the HTML5 Report Viewer, it will be easier to embed the Web Report Designer in an application if it wasn't necessary to manually add the kendo script to the page.
I have a use case which requires me to record data whenever a report is printed. In pursuit of this, I am trying to replace the build in Print() tool and replace it with my own.
I have read this documentation which shows how to remove and reorder the buttons well enough, but it does not support adding a new tool all-together. Javascript event listeners will not work for me because ultimately what I want to do is accomplish a database write, which would be insecure through javascript.
I have been able to establish a workaround by following this documentation and creating a button *outside* of the ReportViewer, however, I would still like to find a way to put the button inside of the ReportViewer toolbar if possible.
Group properties are not visible in the item tree of the Telerik Report Designer for .NET.
I often need to have the same Report Parameters in different reports, including the main and its subreport. Currently, I need to add the parameters manually.
It would be very useful if we could copy/paste Report Parameters between reports.
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.
Old shortcuts(CTRL+INSERT: Copy, SHIFT+INSERT: Paste and SHIFT+DELETE: Cut) of cut/copy/paste don't work in Standalone Report Designer for elements.
As of now the Reporting team provides only part of the source code - mostly the code that targets .NET Framework 4.6.2.
Please expose more of the code to your customers, like Telerik Reporting engine for .NET 6+ and corresponding REST WebAPI.
I have a calculated field of type Decimal where I may dynamically return 0 in some of the rows of data.
If this happens with the first data row, it will not respect the selected data type and will instead infer that the type of data is an integer.
If I use this calculated field in an aggregate function such as Sum(), since the type of the first value will be integer, it will treat the other values as integers as well and the total sum will be incorrectly aggregated.
If I update a StyleRule from the Report Explorer in SRD.NET, the property grid becomes empty afterward, and I have to de-select the rule by selecting another style rule, then select it again to edit another style.
When using the Standalone Report Designer for .NET, the PropertyName dropdown is empty when creating a new style rule with AttributeSelector.
The issue is not present with the Standalone Report Designer for .NET Framework.
If I render a report that includes a HtmlTextBox item with line breaks in its value(<br />) to PDF with the Skia graphics engine and a font such as DejaVu Sans, the <br /> tags are rendered as squares.
Sample HTML:
<p>line1<br />line2<br /><i>line3</i></p>
Using a font such as Arial, there are no such issues. However, before 2024 Q4, it wasn't a problem when using the DejaVu Sans font as well.