I have created a report group, and in that group's header, I have added a textbox with a sorting action.
The action can be triggered, but the data does not get sorted, regardless of whether the sorting target is the report itself or the group from which the group section is created.
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.
Request:
Add a RedisStorage constructor overload that accepts StackExchange.Redis.IConnectionMultiplexer rather than only the concrete ConnectionMultiplexer.
Current behavior:
new RedisStorage(ConnectionMultiplexer connectionMultiplexer) requires the concrete type.
Problem:
Modern ASP.NET Core apps manage a single shared multiplexer through DI and expose it as IConnectionMultiplexer — the abstraction recommended by StackExchange.Redis, and the same type
Microsoft.Extensions.Caching.StackExchangeRedis uses via its ConnectionMultiplexerFactory (which returns IConnectionMultiplexer). To call RedisStorage we are forced to downcast our IConnectionMultiplexer back to
ConnectionMultiplexer. This is fragile and it prevents passing test doubles or decorators (e.g. for instrumentation/logging).
Proposed change:
Add RedisStorage(IConnectionMultiplexer connectionMultiplexer), plus a databaseNumber overload (RedisStorage(IConnectionMultiplexer connectionMultiplexer, int databaseNumber)). ConnectionMultiplexer already
implements IConnectionMultiplexer, so this is fully backward-compatible — existing callers that pass a concrete instance keep working unchanged. Everything RedisStorage needs is available on the interface
(GetDatabase for string operations and LockTake/LockRelease, GetSubscriber, GetServer).
Benefits:
- Clean dependency-injection integration with a shared, app-managed multiplexer.
- Unit-testability via a mocked IConnectionMultiplexer.
- Consistency with StackExchange.Redis guidance and Microsoft's own caching abstractions.
Note:
Please target the maintained Telerik.Reporting.Cache.StackExchangeRedis package (the .2 variant appears discontinued after 18.2.24.806 and has no 19.x/20.x release).
I am trying to use the following HTML content for the HtmlTextBox item:
<span style="font-weight:bold">Label 1:</span> <span>Data 1</span> <span style="font-weight:bold"> Label 2:</span> < span>Data 2</span>
However, the non-breaking space between the spans (label 1/data 1 and label 2/data 2) is not preserved.
When I have multiple reports open in the Standalone Report Designer, I am not able to rearrange/reorder them.
Refer to the tab behavior in Visual Studio, where you can drag one tab and move it to be in front of another tab.
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.
If the Telerik.ReportViewer.WinForms.ReportViewer.ReportSource property of the WinForms Report Viewer is null, besides displaying a message that no report has been loaded, the parameters area is also visible.
The parameters area shouldn't be visible when no report is selected, only the message should be displayed in the viewer's viewport.
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, logarithmic axes do not support the LabelStep and MajorStep properties, which makes it difficult to control label density and avoid visual clutter for larger data ranges.
Adding support for these settings (similar to numerical scales), or providing a way to conditionally hide axis labels, would significantly improve readability and axis customization.
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.
I am using the HTML5 report viewer and seeing 4 errors in the WAVE tool, along with multiple alerts. See: https://wave.webaim.org/report#/https://demos.telerik.com/reporting/product-sales
Please consider addressing them.
Currently, when you set SplitWorksheetOnPageBreak to True, the Excel Sheet name is formed from the DocumentName or ReportName and the number of the page.
It would be very helpful if the report authors can manipulate these names with Expressions.
When generating PDF/UA files, we need to have special objects that are read by an internal system but ignored by screen readers. This cannot be achieved with the existing functionality.
It would be beneficial if we could configure reports so that specific objects inside the generated document are ignored by screen readers. For example, by setting a special value to the AccessibleRole property of a text box.
On export to MS Word, a numbered list that spans two pages restarts at (1) on the second page. Instead, the numbered list should continue numbering from the first page.
For example, if a list has five items and the fourth item starts on a new page, when I export the report to MS Word, the first three items are numbered (1), (2), and (3), and the last two items are numbered (1) and (2) again. The last two items should be numbered (4) and (5).
In addition, if an item in a numbered list splits between two pages, the item is numbered twice: once at the beginning of the item and again on the first line that appears on the next page. The line at the top of the second page is numbered (1). This second number should not appear.
The attached file shows both these issues.