StackTrace of the error:

 System.NullReferenceException: Object reference not set to an instance of an object.
   at System.Collections.Generic.Dictionary`2.TryInsert(TKey key, TValue value, InsertionBehavior behavior)
   at Telerik.Reporting.Interfaces.LocalizationContext.GetString(String resx, String key)
   at Telerik.Reporting.SRDescriptionAttribute.get_Description()
   at Telerik.Reporting.Expressions.EnumContextManager.GetItem(Type enumType)
   at Telerik.Reporting.Processing.ReportExpressionContext.RegisterAllReportingEnums()
   at Telerik.Reporting.Processing.ReportExpressionContext..ctor(Type reportType, AssemblyRefManager assemblyRefManager)   at Telerik.Reporting.Processing.ReportParametersManager`1.CreateExpressionContext(Report report, IList`1 runtimeParameters, AssemblyRefManager references)
   at Telerik.Reporting.Processing.ReportParametersManager`1..ctor(Report definitionReport, IEnumerable`1 definitionParameters, IDictionary`2 reportSourceParameters, IDataProviderContext dataProviderContext, AssemblyRefManager references)
   at Telerik.Reporting.Processing.DocumentParametersManager`1.CreateManager(Report definition, IDataProviderContext dataProviderContext, IParameterValueParser parameterValueParser, IDictionary`2 rsParameters, AssemblyRefManager references)   at Telerik.Reporting.Processing.DocumentParametersManager`1.CreateManagers(IProcessingContext context, IParameterValueParser parameterValueParser)
   at Telerik.Reporting.Processing.DocumentParametersManager`1..ctor(ResolvedReportDocument resolvedReports, IProcessingContext processingContext, IParameterValueParser parameterValueParser)
   at Telerik.Reporting.Processing.ReportProcessor.ProcessReportSource(ReportSource reportSource, IRenderingContext context)
   --- End of inner exception stack trace ---
   at Telerik.Reporting.Processing.ReportProcessor.ProcessReportSource(ReportSource reportSource, IRenderingContext context)
   at Telerik.Reporting.Processing.ReportProcessor.ProcessReportSource(ReportSource reportSource, Hashtable deviceInfo, IRenderingContext context)
   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.RenderReport(String format, ReportSource reportSource, Hashtable deviceInfo, CreateStream createStreamCallback, String& documentName)

Reporting environment:                                                                                      

• UWP using the web viewer
• Odata web service to retrieve data (Web service data source)

The problem: I have a table that has several million records. I have a report with parameters to query those records. Example on a sales report: Customer (All or specific customer) and Product (All or specific product) and date range.  If by mistake the user selects all customers, all products, and a date range of 10 years, he may get millions of records for the report.  After several seconds he realizes that he entered the wrong parameters and wants to cancel the report.  There is no way to cancel. The solution was to run this in another thread and kill the process. That seems like a hack and doesn’t stop the web request so the web service keeps working even after the report has been killed.

Change request: Allow canceling in two ways:

1. The report viewer (we are using the web viewer) should have a cancel button
2. We should be able to cancel a report programmatically. 

The web data source should implement the “Cancellation Token” and cancel the web request when the report is canceled.  Postman, browsers, and other tools use this technique so that the web service understands that the data is no longer needed and it can stop the request.

Some links explaining how to implement Cancellation Tokens:

• https://docs.microsoft.com/en-us/dotnet/api/system.threading.cancellationtoken?view=netframework-4.8
• https://docs.microsoft.com/en-us/dotnet/standard/threading/cancellation-in-managed-threads

Currently, if you delete the default Table Headers from a Table in the Report Designer, it is not possible to re-add it, for example from a menu. It will be good to add such a possibility, as the accidental deletion of the header row may be quite inconvenient for report builders.

If you select a node in the Document Map tree, go to the corresponding reporting item and then scroll away from this position in the Report, the selected Document Map node will remain unchanged and will not correspond to the actually displayed Report item. Moreover, if you would like to return to the Report item selected in the Document Map tree, you will have to select another node and then re-select the desired one.

Hi,

The standalone report designer needs config settings for

• Default Font Name
• Default Font Size
• Default Font Color
• Default Page Settings
  • Margins
  • Unit of Measure
• Snap To Grid

I find that I have to set each of these for every report. 

Please add these,

Karl

Please develop an html5 / Angular JavaScript ReportViewer that works with Microsoft SQL Server Reporting Services (SSRS).  You would sell TONS of it!

 

YES, I'm aware you have a ReportViewer that works with your server reporting solution.  but your reporting solution does not scale.  Furthermore, we have TONS of SSRS reports we don't want to re-write.  It would be way too expensive!  Thanks for your consideration. 

This will prevent file caching.

As in Ticket with ID 1440072 requested we are looking for a funktionallity to send Reports via E-Mails with the WPF ReportViewer. As only the HTML-5 ReportViewer currently supports the E-Mail sending we would request the feature for WPF as well.

 

Best Regards,

Martin

Exporting a report with enabled accessibility to PDF or TIFF formats results in ArgumentOutOfRangeException.

My report consists of a Report Header and a Detail section. Their design-time height is totally less than 20mm. There are no PageBreaks or GroupPageBreaks and all KeepTogether properties are False. In Print Preview, the Detail section starts from the second page when the PaperSize Height is 88mm or less. This is not expected as there is sufficient space left after the Report Header. The Detail section starts rendering from the first page only when the paper height is more than 88mm, which is the expected behavior.

See the forum post Report Header and Detail Section does not print together for the report definition that allows reproducing the issue.

The MsSqlServerStorage class uses a hard-coded string "TR" for its ApplicationName attribute in the connection string. This hard-coded string should be configurable and should not overwrite already existing ApplicationName attribute, if set.

Hi Telerik Team,

 

We are having report parameters up to 30. For better UX we need to group parameters into sections. Please add this feature.

 

Attached is an example of what we want to achieve.

Currently, it is impossible to access the DataSource parameter values after they have been evaluated from the expressions in the report definition. The data from the data items cannot be accessed either. In some scenarios, it will be very helpful to be able to access this information, for example, in the report events.

Multi select parameter selection is not correct when the Kendo version 2020.2.617 is used.

Hi there,

Adding an external style sheet to a report in a report-book triggers an error when previewing the report book, "Object reference not set to an instance of an object" 

I've attached the bare minimum project to reproduce the error.

I've also tried upgrading to R3 2020

Cheers

Currently, when using the ODBC Microsoft text driver to connect to a text file, the Query Designer in the Standalone Designer throws Object Reference Not Set To An Instance of an Object exception.

The result from the PageExec function is null when rendering the report in XLS and XLSX format from the Html5 Viewer and the Standalone designer.

Currently, the MsSqlServerStorage CommandTimeout is with the default value that is 30 s. In some scenarios, like when the Search functionality is enabled and the report is very big, the generated ClientSearchItemsResource may be too big, and when attempting to save it in the storage the latter may throw the exception 'System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.'

The error may be avoided if the CommandTimeout can be increased.