In my report, there are multiple stacked Panels. Each of them may fit on a single physical page. They all have KeepTogether set to True and I expected each of the Panels to start on a new page as two of them cannot fit on one page. This may not happen when I have Page sections though.

When I delete the PageHeader and/or PageFooter the Panels are displayed as expected. However, if I set the Visible of the Page sections to False, the problem persists.

It looks like the Page section's Height is taken into account when evaluating the KeepTogether behavior even for the pages where it is hidden. This shrinks the available physical area and the Reporting engine decides that the Panel cannot fit there, hence the next Panel starts from the current page rather than the next page as I think is correct.

My report contains emojis, and they are displayed properly in the designer and in the Html5 Viewer.

When I export to PDF, the emojis disappear. The emoji font is listed as embedded in the PDF file. Even if I embed the full font, the emojis are not displayed.

I want to export a Report as a PNG image with transparent background.

I set the Style > Background to Transparent for the PictureBox in the detail section, for the Page and Detail sections, for the Report itself, and for Report > PageSettings. The PNG image is still rendered with white background.

Currently, I am using XmlSerializer to deserialize .trdx file, and it returns Telerik.Reporting.Report type object.

Since, for a long time, I need to add my own functions to be available in the report's expressions, and this need becomes larger and larger, it would be great if I could use the Telerik.Reporting.XmlSerialization.ReportXmlSerializer class to deserialize the .trdx file in my derived class.

For example:

var report = new Telerik.Reporting.XmlSerialization.ReportXmlSerializer().Deserialize<MyReportDerivedClass>(TemplateStream);

I noticed that using the Standalone Report Designer for .NET, I can't open the "ReportSource" dialog for a SubReport. The property cannot be edited from the Properties tab either.

Instead, when using the Standalone Report Designer for .NET Framework everything works fine.

Hello Support-Team,

in the WebReportDesigner, the Edit-Window shows "undefined" for the FieldNames, when selected a second Time.

This is also reproduceable in the demo application: https://demos.telerik.com/reporting/designer.

(see Screenshot in attached Files)

Steps to repoduce:

1. Open the Edit-Window for a TextBox (with a DataSource)

2. Select the DataSource-Entry.

3. Select some other Entry, e.g.  "Report Parameters"

4. Select the DataSource-Entry.

Best regards

Alexander Schneider

System Development | Loy & Hutz Solutions GmbH

Currently the generated accessible PDF documents contain tagged elements, but lack information about the logical structure of the PDF document. This prevents screen readers of correctly reading the PDF document contents. The tools like PAC (PDF Accessibility Checker) do not display correctly the document structure.

Currently the behavior of the Web Designer and Standalone Designer is different in regard to DateTime Report Parameters and its "Kind" property.
The Web Designer will assume the value is of Kind "Utc" and the Standalone Designer uses "Unspecified".

This recently became more of an issue since the newer PostgreSQL Provider versions are a lot more strict regarding the "Kind" property:
Npgsql: Timestamp rationalization and improvements

The consequence of this is not being able to use Sql parameters which will work in both the WebDesigner/WebViewer and the StandaloneDesigner:

To resolve this issue right now, one would need to resort to ugly workarounds:

• Add a custom function which receives a DateTime "d" and DateTimeKind "k" value and returns the DateTime value "d" with the Kind set to "k"
  • Having to include a user dll to add that function seems overkill
  • You will need to change every report currently in use
• Change the behavior of the WebDesigner to match the behavior of the Standalone Designer by using a custom IReportSourceResolver, manipulating currentParameterValues 
  • The Kind Property is set to "Unspecified" which is arguably the worst option to take between the three

To properly address this issue it needs to be possible to set the Kind property in the Viewer. Or at least the behavior between the WebDesigner and Standalone Designer should be the same.

Additionally/Alternativly it should be possible to set the target Kind in the Report Parameter.

With kind regards,
Dominik Rothert

Reproducible in 17.1.23.606 - SRD .NET6

Steps to reproduce the behavior:

1. Open Product Sales report
2. Click on textBox3
3. Select "Split cells" from the context menu.
4. Click "Undo"

Expected behavior
No exceptions
Actual behavior
Table Body has 9 rows but 3 are expected.

Screenshots
Screenshot

Reproducible in 17.1.23.606 - SRD and WRD.
Not reproducible with demo report Product Catalog.

Steps to reproduce the behavior:

1. Create new report
2. Add ToC Section
3. Add textbox item
4. Preview the report

Expected behavior
Textbox is shown.

Actual behavior
System.NullReferenceException: Object reference not set to an instance of an object.
at Telerik.Reporting.Processing.DocumentMap.DetermineNodeVisibilityRecursive(BookmarkNode node)
at Telerik.Reporting.Processing.TocSection.MeasureContent(IMeasureContext context, SizeLU availableClientSize)
at Telerik.Reporting.Processing.LayoutElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.VisualElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.ProcessingElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.StackLayout.MeasureContent(IMeasureContext context, SizeLU availableClientSize)
at Telerik.Reporting.Processing.Group.MeasureContent(IMeasureContext context, SizeLU availableClientSize)
at Telerik.Reporting.Processing.LayoutElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.VisualElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.ProcessingElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.StackLayout.MeasureContent(IMeasureContext context, SizeLU availableClientSize)
at Telerik.Reporting.Processing.Report.MeasureContent(IMeasureContext context, SizeLU availableClientSize)
at Telerik.Reporting.Processing.LayoutElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.VisualElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.ProcessingElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.LayoutElement.Measure(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.LayoutElement.MeasureElement(LayoutElement elementToMeasure, SizeLU availableSize, IMeasureContext context)
at Telerik.Reporting.ImageRendering.ImageReportInteractive.MeasureRootCore(LayoutElement root, PageSettings pageSettings)
at Telerik.Reporting.BaseRendering.RenderingExtensionBase.Render(LayoutElement root, Hashtable renderingContext, Hashtable deviceInfo, CreateStream createStreamCallback, EvaluateHeaderFooterExpressions evalHeaderFooterCallback, PageSettings pageSettings)
at Telerik.Reporting.BaseRendering.RenderingExtensionBase.Render(Report report, Hashtable renderingContext, Hashtable deviceInfo, CreateStream createStreamCallback, EvaluateHeaderFooterExpressions evalHeaderFooterCallback)
at Telerik.Reporting.Processing.ReportProcessor.RenderCore(ExtensionInfo extensionInfo, IList`1 processingReports, Hashtable deviceInfo, IRenderingContext renderingContext, CreateStream createStreamCallback)
at Telerik.ReportViewer.Common.ReportRenderer.Render(ReportRendererArgs args)

The report has a single-value nullable parameter with AvailableValues.
When you preview the report in the Standalone Designer, if you checked Null, the value would be respected.
When you preview the report in Html5 Viewer and the parameter value selection is cleared, instead of rendering the report with a Null value, the report is rendered with the last selected value.

Steps to produce in the Html5 Viewer:

1. Select a value from the filter
2. Click the "Preview" button
3. Report generated based on the selected value
4. Click the "clear selection" button and it clears the selected value from the filter
5. Click the "Preview" button
6. Report is generated based on the value selected before it was cleared rather than with Null value

Here is a link to a muted video on how the issue may be reproduced.

If the parameter is not Nullable, the Preview button after step 4 stays enabled, and clicking on it produces the same result as with the Nullable parameter.

In a cascading dropdown, we noticed that the child dropdown is not populated until the parent dropdown is closed after selection. There is a second delay between selecting the parent dropdown and populating the child dropdown. Between this small interval of time, the preview button can be clicked, as it is not disabled, due to which wrong values (previously selected values) are passed in the parameters resulting in incorrect results.

I have cascading parameters, and in some cases, the data set for the dependent parameters is empty. In these cases, the parameter editor of the second parameter is displayed as an input/textbox rather than a dropbox without data.
In the Standalone Designer, the parameter editor is displayed as expected, with a dropdown without data.

The report for reproducing the issue is Product Line Sales-01.zip

In the PDF rendering engine, clipping SVGs is not supported out-of-the-box. Instead, the whole SVG content is rendered without applying any clipping which can lead to differences between previewing the report in the report designer and when exported to PDF. For example:

In design

In the report preview.

In the PDF file.

The following warning is shown in the browser console when starting my Blazor application when I use the native Blazor Report Viewer:

WARNING: Processing source-maps of https://localhost:7025/_content/Telerik.ReportViewer.BlazorNative/js/reporting-blazor-viewer.js took longer than 11000 ms so we continued execution without waiting for all the breakpoints for the script to be set.Could not read source map for https://localhost:7025/_content/Telerik.ReportViewer.BlazorNative/js/reporting-blazor-viewer.js: Unexpected 404 response from https://localhost:7025/_content/Telerik.ReportViewer.BlazorNative/js/reporting-blazor-viewer.js.map: 

In Web Report Designer HtmlTextBox input is just simple TextArea. There is a great need to be able to enter rich text as in a desktop application.

https://docs.telerik.com/reporting/report-items/htmltextbox/overview