<Telerik.ReportViewer.BlazorNative.ReportViewer
                    @ref="reportViewer"
                    ServiceType="ReportViewerServiceType.REST"
                    PageMode="PageMode.SinglePage"
                    ServiceUrl="@(ServiceUrl)"
                    @bind-ReportSource="@ReportSource"
                    AuthenticationToken="@(AuthToken)"
                    ScaleMode="(ScaleMode)ReportSetItem.Report.ScaleMode"
                    @bind-ParametersAreaVisible="@ParametersAreaVisible"
                    Scale="1.5">
                </Telerik.ReportViewer.BlazorNative.ReportViewer>

The variable, ParametersAreaVisible, is set to false. The report viewer is still showing the parameters area. I went back to the designer and set all parameters to Visible = false. When I did this, the parameters area is not displayed.

The report viewer should respect what is bound to ParametersAreaVisible.

Hi,
For our product we were looking into adding additional Request headers to the HTTP requests made by the Telerik Reporting library to the webservice data endpoints for our reports.
We tried adding the headers through a custom DelegatingHandler or HttpClientHandler, but found those were not being picked up.
Not when using the Web Report Designer or Blazor Report Viewer.

Any change we could register such a DelegatingHandler or HttpClientHandler?
Or any other suggestion on a how to add additional headers to the outgoing requests?

The current htmltextbox on the telerik reporter designer does not support html tags for <table>

There is a work around which creates the html text to an image but the quality is not great but more importantly the word wrap functionality is lost.

https://docs.telerik.com/reporting/report-items/htmltextbox/overview#supported-html-tags

Peter

We are trying to upgrade our front end to Angular 17.   When we set the telerik version to 17.2.23.1114, none of the reports open and we are getting the method not found error. 

This is the configuration in our telerik report project which runs .NET 6.

<PackageReference Include="Telerik.Drawing.Skia" Version="17.2.23.1114" />
<PackageReference Include="Telerik.Reporting.Cache.StackExchangeRedis.2" Version="17.2.23.1114" />
<PackageReference Include="Telerik.Reporting.Services.AspNetCore" Version="17.2.23.1114" />

The CSV renderer ignores the visible state of elements in a report definition (sections, headers, footers, text boxes etc.) with the Visible property to false - either explicity or by binding.

This results in much redundant content in the CSV file, that is often not even the actual output/result data - which should be the primary focus of a format like CSV.

Being able to control the output brings much flexibility to the CSV feature. Though Reporting primarily has a focus on a more rich, visual display of data, having access to the same "raw" result set that a report would evaluate can be very useful, without having to try replicate through other means.

Binding the Visible property of elements to: = RenderingFormat.Name <> "CSV" would allow the choice of including what makes sense in the ouput, even allowing a different "view" of the data, which could contain just detail row fields or additionally, summary fields from group and report headers & footers.

It would be nice to have a query builder in the web report designer like in the stand alone report designer. 

While some viewer options such as the pageMode, viewMode, etc. are already exposed and configurable through code, the parameters are not. This means that the viewer will always load the report with the default report parameter values which can troublesome.

For example, I need to be able to pass a JWT to a WebServiceDataSource inside my report and I use a report parameter for doing so. This works as expected when I use a simple report viewer but when the report is loaded by the Web Report Designer, it is not possible to pass a value from the front end where the designer is initialized.

Since upgrade to openXML 3.0.0 we get exceptions at runtime when we want to create a report in XLS.

While a feature request has been filed here: https://feedback.telerik.com/reporting/1631967-openxml-renderings-should-work-with-documentformat-openxml-3-0-0-and-newer one could argue it is a bug. Anyway, i raise this issue here to have some extra attention to it.

System.TypeLoadException
  HResult=0x80131522
  Message=Could not load type 'DocumentFormat.OpenXml.Packaging.ImagePartType' from assembly 'Telerik.Reporting.OpenXmlRendering.2.7.2, Version=17.2.23.1114, Culture=neutral, PublicKeyToken=a9d7983dfcc261be' due to value type mismatch.
  Source=Telerik.Reporting.OpenXmlRendering.2.7.2
  StackTrace:
   at Telerik.Reporting.OpenXmlRendering.Spreadsheet.Worksheet..ctor(Workbook workbook, WorksheetPart worksheetPart)
   at Telerik.Reporting.OpenXmlRendering.Spreadsheet.Workbook.AddWorksheet()
   at Telerik.Reporting.ExcelRendering.Report.Render(IWorkbook workbook)
   at Telerik.Reporting.OpenXmlRendering.Spreadsheet.SpreadsheetReport.Telerik.Reporting.Processing.IRenderingExtension.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.Reporting.Processing.ReportProcessor.ProcessAndRender(String format, ReportSource reportSource, Hashtable deviceInfo, IRenderingContext renderingContext, CreateStream createStreamCallback)
   at Telerik.Reporting.Processing.ReportProcessor.ProcessAndRenderStateless(String format, ReportSource reportSource, Hashtable deviceInfo, IRenderingContext renderingContext, CreateStream createStreamCallback)
   at Telerik.Reporting.Processing.ReportProcessor.<>c__DisplayClass47_0.<RenderReport>b__0(SingleStreamManager sm)
   at Telerik.Reporting.Processing.ReportProcessor.RenderReportSafe(Func`2 renderCallback, String format, IRenderingContext renderingContext)
   at Telerik.Reporting.Processing.ReportProcessor.RenderReport(String format, ReportSource reportSource, Hashtable deviceInfo, CancellationToken cancellationToken)
   at Telerik.Reporting.Processing.ReportProcessor.RenderReport(String format, ReportSource reportSource, Hashtable deviceInfo)
   at Indato.Reporting.TelerikReports.<>c__DisplayClass1_0.<RenderReportAsync>b__0() in C:\Users\leosiepel\Source\Workspaces\Indato\Indato-Main\Indato.Reporting\TelerikReports.cs:line 42
   at System.Threading.Tasks.Task`1.InnerInvoke()
   at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)

Need to allow Excel Export with 10.1.16.615 version on FIPs enbled

Hi Team,

I had tried with the provided post as below with DocumentFormat.openXML.dll verison (2.5) but not working .

please help to resolve this ASAP.

===

Based on what you described and the ticket info, I am assuming that you are getting this error when you render a report in the Excel 97-2003 (XLS) format. Is that correct?

Unfortunately, this is a known limitation of the Excel 97-2003 rendering, and exporting a report to XLS in FIPS-enabled environments will fail. Considering this, I suggest choosing one of the following options for exporting reports to Excel:

• Exporting the report to the newer XLSX format. (See exporting in XLSX)
• Disabling FIPS.

If choose the first option, you can disable the older Excel rendering format so that it is not available as an option when the report is displayed in a report viewer. For example, the following code can be put into the web.config/app.config of the project:

<configuration>

  <configSections>
    <section
        name="Telerik.Reporting"
        type="Telerik.Reporting.Configuration.ReportingConfigurationSection, Telerik.Reporting"
        allowLocation="true"
        allowDefinition="Everywhere"/>
  </configSections>

    ...

  <Telerik.Reporting>
    <extensions>
      <render>
        <extension name="XLS" visible="false">
        </extension>
      </render>
    </extensions>
  </Telerik.Reporting>

   ...

</configuration>

I hope this helps, please let me know if you have any additional questions. Thank you for trying Telerik Reporting!

Regards,
Dimitar
Progress Telerik

Currently the interface for `IReportSourceResolver.Resolve` only allows for a synchronous implementation of `Resolve`. It'd be nice if the interface allowed for an asynchronous implementation, too.

This is in reference to Telerik Reporting API Server with a custom report source resolver.

When I conditionally hide a TextBox in a table, I got unwanted spaces between the hidden boxes.

In my example below I have 30 records as seen in the first table.

In the second table I have the same data, but conditionally formatting it to hide based on the following:

= Fields.Column1 > 2 and Fields.Column1 < 28

Notice the space that shows between 02 and 28.

 https://feedback.telerik.com/reporting/1597971-report-duplicating-items-from-svg-image-when-exporting-to-pdf?_ga=2.194313453.1154414800.1688345672-1157346896.1665952494&_gl=1*fh25sr*_ga*MTE1NzM0Njg5Ni4xNjY1OTUyNDk0*_ga_9JSNBCSF54*MTY4ODU0MDMwNy4zMzguMS4xNjg4NTQwMzgwLjU4LjAuMA

Hey team,
Please kindly speed up about this bug as this affects the project alot. Also would appreciate for the update.

Hello,

in the WebReportDesigner it is currently only possible to add a TypeSelector to a StyleRule. (see screenShot: "WRD_StyleRule_Add_Selector.png").

Interestingly, when a report already contains a StyleSelector, it is possible to edit and save the changes, this is great :-), (see screenShot: "WRD_StyleRule_Edit_StyleSelector.png").

Would be great if we could add a StyleSelector ;-).

Best regards

Alexander Schneider