Hello!

I have a Silverlight application that uses Telerik reporting. Also this application uses Microsoft Prims.
After upgrading from current version of Telerik (6.0.12.215, Q1 2012 Visual Studio 2011 Refresh) to newer (11.1.17.614, R2 2017) issues occurred.
After minor changes in source code (correcting to use right namespaces) solution builds fine, even runs fine, but reports shows nothing useful (no values in parameter-binding fields). So, parameters now do not passes to reports.

This is some source code.

protected void NavigateToPermissionReport()
{
   string navigationSource = AppPages.PermissionReportView + "?" +
   string.Join("&", this.Parameters.Select(parameter => string.Format("{0}={1}", parameter.Key, parameter.Value)));
   this.EventAggregator.GetEvent<NavigateToPageEvent>().Publish(true);
   this.RegionManager.RequestNavigate(AppRegions.NavigationRegion, navigationSource);
}

After this piece of code “black magic” happen and execution comes directly to report’s code:

private void OnPermissionItemDataBinding(object sender, EventArgs e)
{   
    this.ItemDataBinding -= this.OnPermissionItemDataBinding;   
    this.BeginGetPermission(this.ReportParameters);
}

private void BeginGetPermission(ReportParameterCollection parameters){
    PermissionViewModel viewModel = new PermissionViewModel();
    viewModel.LoadData(parameters);
    this.DataSource = new ObjectDataSource(viewModel, string.Empty);
}

What happens between these parts of the code I can’t figure out.

So, before upgrading, parameters in ReportParameterCollection had the same values as in navigationSource, but after, parameters became null.

Why this can happen?

Thanks.

Hello, i have a report made with reporting Q3 2013 and VS 2012. When installing it on the client, it gives error 40: a connection with SQL could not be opened. The report in local is ok. that could be happening? other report in the same app are ok, with de same connection.

I'm using SqldAtaSource with connection defined in web.config.

Thank you

Hello,

We are trying to generate the report viewer report in javascript but are having a difficult time trying to figure out what the javascript logic should be.

When we set the report source on the control tag it works flawlessly. 

For example 

When we try to set the report source in javascript nothing happens.

Example

I have an expression like reportProcessor.RenderReport("XLS", ...) which always throws an exception with message "XLS rendering format is not available" when running in Edge.js via an Electron app, but never throws when running "normally" via a WinForms app. Same assembly, same code, but different behavior.

Stack trace for the exception:

   at Telerik.Reporting.Processing.ReportProcessor.GetExtensionInfo(String format)
   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)
   at [my code]

Other details about the environment:

Telerik.Reporting.dll, version 9.2.15.930

Windows 10

Excel 2016

What kind of conditions would cause XLS rendering to be unavailable?

It's probably important to note that this same body of code has an expression like reportProcessor.RenderReport("PDF", ...) which works totally correctly with both the Edge.js-based Electron app and the WinForms app. This expression executes a few statements before the one for XLS that fails.

I checked that the app domains of both apps are running with full trust because I suspected there might be a lack of unmanaged code permissions, but that's apparently not the problem. Both domains have full trust.

I have failed to setup a project as instructed here:

https://docs.telerik.com/reporting/html5-report-viewer-asp-net-core-2

I have been over the instructions 10 times, the error message I receive is.

Error registering the viewer with the service.

An error has occurred.
The type initializer for 'Lock' threw an exception.

Project found here:

https://www.dropbox.com/s/8rl4hhanj5gbfc9/WebApplication2.zip?dl=0

Hi,

I'm using telerik report viewer in my web application with angular2.I'm able to get the report fine in developing mode but when i try to compile angular2 code using AOT compilation i'm getting following error as attached in screen shot.can any one help me to resolve the issue

Thanks&Rds,

Raghu S

I am looking for advise as to how to capture if a report was actually printed?

This would then be stored in a SQL database as a true/false.

Which event should I be using? Has anyone done this or have sample code?

I want to display a table with width of details section. I am generating this table from code. It looks like this:

My real table has 13 columns and their initial width is computed based on initial table width.

When I generate my report as "Portait" table fills all available width. 

When I change page settings to "Landscape" cell width grows to accommodate content and table fills all available width.

But when I change page settings back to "Portait" then cell contents is not shrunk back and my table spans to three pages.

What can I do be able to switch from Portait to Landscape and back without this effect?

Hi. I need to add some functionality to my application which needs to be triggered on print or export of a report(created in the standalone report designer). I've seen a page in the Telerik documentation stating the following:

"Additionally events can't be used with Standalone Report Designer report documents, because the custom code from events is not serialized in reports."

I've also noticed this behaviour through my own testing.

I'm wondering if there is any way that I can capture when a report is printed or exported from the Telerik Winforms Report Viewer without having to reimplement Windows print/export dialogs.

Thanks.