I am using the Standalone Report Designer for .NET to open a code-based report from an application that was migrated from .NET Framework. Before the migration, function calls defined in the designer.cs file were preserved and evaluated at runtime as expected. However, after migrating to the code-based reports functionality supported by the Standalone Report Designer for .NET, these function calls are evaluated immediately during the report import process, and the resulting values are then serialized and stored in the report definition.

It would be nice if the function calls were preserved in the imported report, allowing them to be evaluated later at runtime, as their return values may change depending on the execution context.

Currently, graph axes do not provide a way to render separator lines between category groups. While this is generally not an issue for simple scenarios, it can make charts with nested categories difficult to read.

For example, when a graph displays multiple subcategories under a parent category (such as revenue ranges grouped by quarter), there is no built-in visual indicator showing where one parent category ends and the next begins.

It would be useful to provide support for category separators on graph axes, allowing report authors to visually separate category groups and improve readability when working with hierarchical data.

I use the exportBegin event to prevent the default export logic. However, when I do that, the default viewer notification remains, and I have to hide it manually:

                    exportBegin: function (e, args) {
                        args.handled = true; // Set to true to cancel the default export behavior.
                        //...
                        $(".trv-notification").addClass("k-hidden");
                    },

Double-click selection in the expression editor isn't context-aware. In almost every other application, double-clicking selects a token based on its surrounding context — a single field/identifier when clicking on a field, or the word boundary within a string literal when clicking inside quotes. The expression editor doesn't respect these boundaries, so its double-click behaviour is inconsistent with the standard expression-editor behaviour users expect.

Expected: Double-click selects the relevant token based on context (e.g. an individual field reference, or a word within a string literal).

Actual: Double-click selection ignores context and does not match the token/word-boundary behaviour found in virtually all other expression editors and text inputs.

I have graphs in my report. I render them with Skia on Linux. The issue reproduces with Skia on Windows as well.

The legend labels are not aligned well with the color icon, and data labels on a horizontal bar chart (with OutsideEnd) are misaligned as well:

If I open the expression dialog in the Web Report Designer and select one of the available functions, I will see a sample snippet in the third column below the expression area.

This column is not selectable, so I cannot copy the example and test it out. This example should be copyable, so that each function can be easily tested in the report designer.

I have localized a report with a Graph in the 'ar-SA' culture.

When exporting to PDF from the viewer, the report is generated as expected. In the Report Viewer's Preview, though, the Graph Legend and Labels are not correct:

I am using Native Blazor Report Viewer, but the problem also reproduces in the HTML5-based web viewers, with all the themes I have tested.

Hi Team,

Even after giving the date format facing the inconsistency in the date field for some rows in the table when we export it to CSV file

<TextBox Width="1.036in" Height="0.24in" Left="0in" Top="0in" Value="= Fields.StartDate" Format="{0:MM'/'dd'/'yyyy h:mm tt}" Name="Opened Date">. please see the attachment

I am trying to use the following HTML content for the HtmlTextBox item:

<span style="font-weight:bold">Label&nbsp;1:</span>&nbsp;<span>Data&nbsp;1</span> <span style="font-weight:bold">Label&nbsp;2:</span>&nbsp;<span>Data&nbsp;2</span>

However, the non-breaking space between the spans (label 1/data 1 and label 2/data 2) is not preserved.

I have a custom assembly with default 'version', 'culture', and 'publicKeyToken'.

When I reference the assembly in the 'assemblyReferences' element only with its 'name', the Reporting Engine recognizes it.

If I reference it with the full version, '1.0.0.0', it also works.

However, when I set the 'version' to '1.0.0', the Reporting Engine throws, stating that the assembly is not trusted and must be referenced in the 'assemblyReferences' element.

The attached sample has a simple table with two row groups, and "header" rows created via "Insert Row -> Outside Group - above".
The groups have "keep together" set.

But despite this, the header rows render at the bottom of one page, with data rows on the following page. This should never happen, I can't think of any case it would be expected (it would be like having "Chapter 2" at the bottom of a page when the text for it starts on the next page). 

I also have a sample with just 1 row group, but with 2 detail rows, and the same thing happens. It only appears to work when there's just 1 row group and 1 detail row.

We have spotted that PInvoke is now marked as deprecated (this applies even to the latest 0.7.124 version). In the description of the PInvoke.User32 NuGet package, it is mentioned that Microsoft.Windows.CsWin32 should be used instead:

Please consider replacing the deprecated package.