Starting in 2019, the Reporting control is no longer included in Essential Studio®. If you're experiencing issues with the Syncfusion� Reporting Platform, Report Viewer, Report Designer, or Report Writer, we recommend migrating to Bold Reports, our dedicated reporting platform.

Bold Reports offers a comprehensive suite of tools and features for all your reporting needs, and we will help you make a smooth transition from the discontinued control. Our support team at https://support.boldreports.com/ is here to assist you with any questions or difficulties you may encounter during the migration process.

We thank you for choosing Syncfusion� and appreciate your understanding.

export function not return

Hello,

Reportviewer show report  normally  but when  request any export  service return  below  error report , 


 xmlns:q1="http://www.w3.org/2001/XMLSchema" xmlns:p2="http://www.w3.org/2001/XMLSchema-instance" p2:type="q1:string">
Sf_Exception - System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary. at System.Collections.Generic.Dictionary`2.get_Item(TKey key) at Syncfusion.EJ.ReportViewer.ReportHelper.ProcessReport(Dictionary`2 jsonResult, IReportController reportController)


i think problem is sending parameters , when call report show, run parameters :

{"reportAction":"ReportLoad","controlId":"tekneler_reportViewer_Control","reportPath":"Tekneler.rdlc","reportServerUrl":"","processingMode":"Local"}


but when call  export mode, i see parameters  not json  format:

controlID=22B2E0A3-20E5-622A-47EE-2189D60FDB9D%40tekneler_reportViewer_Control&resourcetype=PDF&isPrint=false&reportName



when  debug our api i see in reportviewer controller ,  PostReportAction functions  Dictionry parameters empty, when calling export.


sorry for poor english.






5 Replies

YD Yuvaraj Devarajan Syncfusion Team October 24, 2017 12:43 PM UTC

Hi Nedim, 

Thanks for contacting Syncfusion support. 

We have checked the mentioned export problem in ReportViewer and it’s working properly at our end. We suspect the mentioned problem might be occurred when using hidden items or report items split into multiple pages. So, can you please share your issue reproducible RDL/RDLC file to validate the mentioned problem at our end and It will be helpful for us to resolve the mentioned problem at earliest.  

Regards, 
Yuvaraj D. 



NE nedim October 25, 2017 09:49 AM UTC

Hello, 

I think problem is wep.api  handling/routing.

I use previously downloaded  x:\Syncfusion\15.3.0.26\JavaScript\ejservices\App_Data\Reports\Product Catalog.rdlc  fro test.

I run  x:\Syncfusion\15.3.0.26\JavaScript\ejservices   web.api  service in local, and syncfusion angular 2 example offline (sample report path routed to local server)  ,  no problem. I see report and  I get export content.

But when use our web api  , report show, report print  is ok,  but when requesting  export to any options, request goes to controller, I see with debugger , but not return export content.

     Our  web.api  version  2.0 and use  .net 4.5.1 . and config route is,

            config.Routes.MapHttpRoute(

                name: "ActionApi",
                routeTemplate: "api/{controller}/{action}",
                      defaults: new {action= RouteParameter.Optional}
                );




YD Yuvaraj Devarajan Syncfusion Team October 26, 2017 05:00 AM UTC

Hi Nedim, 

We suspect the mentioned problem might be occurred when export dependent assemblies are not referred in your WebAPI application. So, we request you to refer the ReportViewer export dependent assemblies in your application. Also, please ensure the same build version and framework version assemblies are referred in your application. Please find the list of Syncfusion ReportViewer dependent assemblies, 
  • Syncfusion.Linq.Base
  • Syncfusion.Compression.Base
  • Syncfusion.Presentation.Base
  • Syncfusion.OfficeChart.Base
  • Syncfusion.EJ
  • Syncfusion.EJ.ReportViewer
  • Syncfusion.Pdf.Base
  • Syncfusion.XlsIO.Base
  • Syncfusion.DocIO.Base
  • Syncfusion.Shared.Wpf
  • Syncfusion.Chart.Wpf
  • Syncfusion.Gauge.Wpf
  • Syncfusion.SfMaps.Wpf

Please refer to the below UG documentation link for more detail, 

We have prepared a simple sample and it can be downloaded from below location, 

If the issue still persists, then share the issue reproducible RDL file or revert the shared sample with issue reproducible procedure to validate the mentioned problem at our end. 

Regards, 
Yuvaraj D.  



NE nedim October 30, 2017 01:22 PM UTC

Hello Again,

Thank your support.
I download this base  projects and compiled, report  show  ok, but Export function returns error.
I spent a lot of time, but I failed in the export process.  :( 




  HTML code for report:

<h1>
    {{title}}
</h1>
   <ej-reportviewer id="territorysales_reportViewer_Control" [reportServiceUrl]="serviceUrl" [processingMode]="localMode"  [reportServerUrl]="serverUrl"
    [reportPath]="reportPath" [dataSources]="reportData" [parameters]="parameters">
</ej-reportviewer>

TS code for report:

import { Component, ViewEncapsulation, ViewChild } from '@angular/core';
import { EJComponents } from 'ej-angular2';
@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.css']
})
export class AppComponent {
   title = 'app works 2!';
    public serviceUrl: string;
    public serverUrl: string;
    public localMode : string;
    public reportPath: string;
 public parameters: any;
 public reportData: any;
    constructor() {
        this.serviceUrl = 'http://localhost:49771/api/ReportApi';
          this.reportPath = 'Product Catalog.rdlc';
         this.localMode = 'Local';
       
    }  
}

my sample api  attached, it use  syncfusion  standart report example   Product Catalog.rdlc  and sample List data retuns.



Attachment: webapiapi_29fcc013.zip


YD Yuvaraj Devarajan Syncfusion Team October 31, 2017 09:10 AM UTC

Hi Nedim, 

Thanks for the update. 

We have checked the mentioned export problem in the shared sample and its working properly at our end. We suspect the mentioned problem might be occurred when different build version and framework version of Syncfusion dependent assemblies are referred in your application. So please ensure the same build and framework version Syncfusion dependent assemblies are referred properly in your application. 

If the issue still persists, then share the issue reproducible screenshot and RDL file to validate the mentioned problem at our end.  

Regards, 
Yuvaraj D. 


Loader.
Up arrow icon