The Telerik.Reporting documentation mentions that the Telerik.Reporting.* libraries should be available on nuget.org with the most recent release. However, when I search for Telerik.Reporting in the NuGet Gallery, I am not able to find any Telerik.Reporting.* package. The other products we use (UI for WPF, Document Processing) seem to be available though.
-----------------------------------------
Staff note: On the Reporting side, our initial goal was indeed to make Telerik Reporting available through nuget.org, alongside the rest of the Telerik product portfolio. However, we are currently investigating an issue that is preventing us from publishing the Telerik.Reporting packages to nuget.org, which has delayed their availability.
Please use this feedback item to subscribe to updates and receive a notification as soon as the Telerik.Reporting packages become available on nuget.org.
When I render a report with Gujarati language text to PDF on Windows, the GDI graphics engine is used and the text is displayed properly.
When I render the same report with the Skia graphics engine, on Windows or Linux, the characters are misplaced or incorrectly drawn.
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.
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.
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.
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.
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.