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.
It would be great if you could introduce the ability to create custom reusable color palettes in Telerik Report Designer, so I don't have to declare the same set of colors for each chart I need them.
If you have a lot of graphs in your report then it is more convenient to change the color palette one place.
When using screen reader applications like JAWS or Narrator, those tools read accessible reporting PDFs in an incorrect order. For example, if I have two items in the report, the reader will read the second item first.
Additionally, images whose AccessibleDescription I have set may be read multiple times..
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:
When I display a report in a web report viewer, whose service is running on a server where one or more of the used fonts are not available, the first instance of the item(s) that use those fonts is being substituted with another font. The rest of the items do render with the original font, however.
This creates confusion and inconsistency. We should use the substituted font because it's used for measuring when using Print Preview mode in the web viewers, or when rendering to pdf via print/export.
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.
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">
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).
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.
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.
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.
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.
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.
However, in my report, the Interactivity options do not show any property for Level. I am only seeing basic properties like Action, BookmarkId, DocumentMapText, TocText, etc.
The Level field is completely missing.