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

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.

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