Group properties are not visible in the item tree of the Telerik Report Designer for .NET.

The report items that have explicitly set background in the report definition are not highlighted by the Search functionality of the viewer when their content matches the search.

Reproducible with Blazor Native Report Viewer.

Partially reproducible with HTML5 Viewer - the highlighted (when selecting the item in the Search list) class is applied but the shaded is not.

The workaround is to use the following styles on the page with the viewer:

<style>
    .trv-report-viewer-wrapper .trv-search-dialog-highlighted-result {
        background-color: rgba(0, 35, 102, 0.3);
        color: #fff;
        background-image: none;
    }

    .trv-report-viewer-wrapper .trv-search-dialog-shaded-result {
        background-color: rgba(255, 140, 0, 0.3);
    }
</style>

In the WebReportDesigner, when resizing a table cell on the designer-Element (NOT through the properties area), the Units of width and height are always reset to pixel.

The selected unit should not change when resizing the table cell/column/row.

We use some cascading/dependant parameters and, in some cases, these have their "value" property (initial/default) value unset, generally to prevent the viewer auto-run as well as to give the user a chance to select first.

The dependant parameters have their Value properties set to the ValueMember field(e.g. =Fields.value) so when the cascading parameter is selected, the dependant will have a valid value set.

However, the "missing or invalid parameter" still shows that the dependant parameter has an invalid value.For example:

In some cases, the engine will not render the graph and will instead display the message 

The current NumericalScale settings would result in more than 1000 labels which will make the scale unreadable. Please set the axis/ grid lines visibility to False or change the corresponding property.

The reason to see this or similar messages is that the selected LabelStep, MajorStep, or MinorStep scale property has a value that is too small and the processing engine will violate the previously mentioned constraint numbers.

The issue is fixed by manually correcting the values for those properties but I wish that the automatic configuration would be better.

Currently, there is design-time support for the WinFoms Report Viewer in the VS Designer only when the project targets .NET Framework.  I need this functionality to be supported in .NET WinForms projects as well.

I followed the instructions from the Loading .NET 9 assemblies in the Standalone Report Designer for .NET - Telerik Reporting article to use the Standalone Report Designer for .NET with the .NET 9 runtime so that I can load .NET 9 assemblies in it but it crashes on startup:

When trying to open reports from an assembly in the Standalone Report Designer so that they can be imported, if there are types that inherit from Telerik.Reporting.Report that do not have a parameterless constructor, this will cause an exception as it is required for the report types to have such a constructor, otherwise, the wizard cannot import them into TRDP.

In this scenario, the report types that do not have a parameterless constructor should be written to the trace or in the exception message dialog so that the user can see which are the problematic types and correct them.

I have created an abstract class in my report library that inherits from Telerik.Reporting.Report. When I try to load the project's assembly in the Standalone Report Designer to import those reports as TRDP, an exception is thrown while the application tries to load the assembly that there are report types that do not have a parameterless constructor.

To resolve the issue, I had to remove the 'abstract' modifier. However, that should not be necessary. The wizard should ignore abstract classes or at the very least, let me import the other report types while displaying a message that there are report types with parameterless constructors.

Hello,

the search results in a PDF generated with report is not correct. Again...

Please fix this bug and add this scenario to your tests.

Steps: Search for a text in a pdf.

When exporting an SVG image to PDF, polylines with stroke-dasharray are rendered incorrectly — the dash pattern is not applied.

Additionally, polylines with a stroke-width exhibit visual artifacts such as pixelation or inconsistent thickness.

Step by step instructions or code snippets how to reproduce the problem

1. Save svg content (see below) as a file c:\test_svg_line_stroke.svg
2. Create an empty report
3. Add a picture box
4. Select a value for the picture box - use file c:\test_svg_line_stroke.svg
5. Go to preview - SVG is correct
6. Click Export->Acrobat (PDF) file and export a PDF file
7. Open PDF file to verify that the red line in a bottob does not have stroke-dasharray applied

If there's no black line with no stroke-dasharray - the red line in a bottom looks correct

test_svg_line_stroke.svg

<svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xml="http://www.w3.org/XML/1998/namespace" width="500" height="400" viewBox="0, 0, 500, 400" preserveAspectRatio="xMinYMin" transform="scale(1)">
  <polyline points="100, 100 400, 100" stroke-width="7" stroke-dasharray="40 40" style="fill:none;stroke:#FF0000;" />
  <polyline points="100, 200 400, 200" stroke-width="5" style="fill:none;stroke:#000000;" />
  <polyline points="100, 300 400, 300" stroke-width="7" stroke-dasharray="40 40" style="fill:none;stroke:#FF0000;" />
</svg>

test_svg_line_stroke.svg - svg source file 
test_svg_line_stroke.trdp - report with a picture box with SVG image
test_svg_line_stroke.pdf - generated PDF file

I have multiline text in a TextBox item that has its Style > TextAlign set to Center.

It is rendered as expected with the GDI+ graphics engine.

When I switch to the Skia graphics engine in the Standalone Designer .NET, though, some lines are not centered correctly in PDF rendering:

In Preview of the designer, with PNG and OpenXML export the text is shown as expected.

We'd like to have a settable property on the web designer and report viewer which takes a function which returns an access token.
This way a new access token can be requested by the designer/viewer when the current one expires.

This is usually used in the following way:

1. Implement a function with signature "string GetAccessToken()"
2. Set that function to the property AccessTokenProvider of the designer/viewer
3. Designer/Viewer wants to make a request and fetches and caches the access token
4. Designer/Viewer uses that access token until it hits a 401 upon which
   1. The Cached access token is cleared
   2. A new Access token is fetched from AccessTokenProvider and then cached
   3. Retry the request with the new access token
   4. Should the retry also fail return the failure

Should the above be to specific/inflexible:
Instead of caching the access token, call AccessTokenProvider for every fetch but also provide an additional parameter with the "reason" for the call, so the implementer of AccessTokenProvider can decide themselves when to return a cached AccessToken or generate a new one.

When the report contains SVG images with Arc segments, the rendering with Skia may result in the following exception:

Telerik.ReportDesigner.Net Error: 0 : System.InvalidOperationException: Invalid image data.
 ---> Telerik.Drawing.Skia.Exceptions.SkiaNotSupportedException: Exception of type 'Telerik.Drawing.Skia.Exceptions.SkiaNotSupportedException' was thrown.
   at Telerik.Drawing.Skia.Drawing2D.GraphicsPath.AddArc(RectangleF rect, Single startAngle, Single sweepAngle)
   at Telerik.Reporting.Svg.SvgRectangle.Path(ISvgRenderer renderer)
   at Telerik.Reporting.Svg.SvgVisualElement.Render(ISvgRenderer renderer, Boolean renderFilter)
   at Telerik.Reporting.Svg.SvgVisualElement.Render(ISvgRenderer renderer)
   at Telerik.Reporting.Svg.SvgRectangle.Render(ISvgRenderer renderer)
   at Telerik.Reporting.Svg.SvgElement.RenderChildren(ISvgRenderer renderer)
   at Telerik.Reporting.Svg.SvgElement.Render(ISvgRenderer renderer)
   at Telerik.Reporting.Svg.SvgFragment.Render(ISvgRenderer renderer)
   at Telerik.Reporting.Svg.SvgDocument.Draw(ISvgRenderer renderer, ISvgBoundable boundable)
   at Telerik.Reporting.Svg.SvgDocument.Draw(Int32 rasterWidth, Int32 rasterHeight)
   at Telerik.Reporting.Processing.Imaging.SvgImageItem.CreateBitmapImage(RadSvgImage svg, Size targetSizePx)
   at Telerik.Reporting.Processing.Imaging.SvgImageItem.DrawImage(RadSvgImage svg, CreateImageContext context)
   at Telerik.Reporting.Processing.Imaging.SvgImageItem.CreateImageCore(CreateImageContext context)
   at Telerik.Reporting.Processing.Imaging.ImageItemBase.CreateImage(CreateImageContext context)

If I set the ReportSource to the Native Blazor Report Viewer using @bind directive, for example:

@bind-ReportSource="@ReportSource"

ReportSource="@(new ReportSourceOptions { ... })"

It causes the viewer to go into a loop of trying to set the ReportSource, and it never renders the report.

My use case is a multi-select parameter that is based on a dataset; and the dataset is filtered by 2 other parameters.

The dependent parameter editor is shown as a SpinButton rather than a multi-select editor in the Blazor Native Report Viewer: