The issue is caused by an issue in the SQL DataSource Wizard that doesn't provide the correct Data Provider name. In the wizard on the first page, the Data Provider must be MySql.Data.MySqlClient, but the option is limited only to MySql.Data. Since the engine cannot determine the type of the data provider by that name, it falls back to System.Data.SqlClient and claims that "Port" is not a supported keyword.
The workaround is to avoid using the SQL DataSource wizard and edit the data source properties directly in the properties grid. You can check the attached silent video that demonstrates how to do so.
When exporting a report to Excel with the UseExtendedFormatting parameter set to False, the Standard DateTime Format Strings are hard coded as custom formats in the generated XLS/XLSX document.
The custom formats correspond to the current regional settings or, if the report is rendered with a specific culture, the default date format strings for the selected culture.
I have an SVG image that includes text, which uses the "Arial" font-family. On Windows, it renders correctly with GDI and SKIA. However, on Linux, an "Invalid Image Data" exception is thrown, and the image is not rendered. This happens when exporting to PDF and XLSX.
Furthermore, even though there is an exception, it is not caught by the Reporting engine, so RenderingResult.HasErrors returns false. The logic should be modified to catch this error and update the HasErrors flag.
So far, the issue seems to be specific to the Arial font. When I change font-family, the PDF document is created as expected.
I have a CS report that contains a SubReport with InstanceReportSource. I have it in a .NET 10 Classlibrary project.
I tried to edit this report as a coded report in SRD.NET. However, when I saved the report, in the 'designer.cs' file, the value assigned to the ReportSource of the SubReport was set to 'userreport1' that is not instantiated and throws.
When adding localization in CS reports in the VS designer for .NET Framework 4.6.2, the latter adds calls to the ApplyResources function when setting report item values.
After editing and saving such coded reports in SRD.NET, though, they are deserialized differently, replacing the ApplyResources function calls with hardcoded strings. This breaks localization, although the resx files remain.
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.
As we install fonts regularly and don't want to restart/redeploy everytime we install a new font we propose a new api to clear the cache.
A new method Telerik.Reporting.Fonts.RefreshCache would solve this problem and improve the experience of using the Telerik Reporting library.
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.