Some Arabic words are aligned incorrectly when PDF export is executed using Skia Graphics Engine.

In PDF exported reports some of the characters (and sometimes entire words) disappear. Some of the characters disappear only under Linux.

We have text box that needs to show all that it can without growing.

If text box is set to CanGrow = false. Text box does not grow as expected however it will wrap the text.

Setting text box to TextWrap = false and CanGrow to either true or false. When rendered using GDI+ it renders as expected.  When rendered using Skia it appears to always wrap the text.

Reports are deployed to a Linux docker image which is configured to use the Skia rendering engine.

Screenshot output using GDI+

Screenshot output using Skia

 

The OpenXML formats should expose a device setting such as the ValidateXmlCharacters setting in the WPFXAML/WPFXAMLInteractive Device Information Settings that specifies whether Unicode characters that are not XML compliant, should be allowed in the report or a built-in utility function that I can invoke on the data fields to filter out those invalid characters.

I have set the AllowNull setting of the parameter to True but even after I clear the selection and click on the "Preview" button, it sends the last selected value instead of null.

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 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.

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.

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.

Change all invocation with the database to use Store Procedure instead of direct access to table/view, allows developer to implements it own database design struct/methodology and security/policy.

In all projects i have changed the Reports tables names to follow the design struct/methodology defined for the project. All reports store Procedure was changed to reflect this design change.

In my case, the QueryDeleteBehavior can't be implemented without maintain the design methodology/policy.

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. 

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.

Hello,
Once a chart has been inserted, the Wizard cannot be reopened. Frankly, navigating through the hundreds of chart properties is counterproductive. There should be more ways of modifying properties via a wizard that can be recalled once the chart is in the report.
Thanks for your time,

I want to be able to apply a grayscale filter when I render the report in PDF format.

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.

 

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.

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.  

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.

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.

 The design-time preview of the PictureBox throws a null reference exception when it has a binding that changes its value based on one of the fields from the data source. The preview incorrectly tries to respect this binding which will not work in design time as the data is not fetched at this point. Instead, the design-time preview should use the default value from the Value property of the PictureBox, which is what the standalone designer does.

This does not affect the actual report preview.