Tablix performance issue - with larger dataset

Tablix performance issue - with larger dataset

Posted by: grapecity on 5 January 2018, 2:20 pm EST

• 

  grapecity

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 5 January 2018, 2:20 pm EST

  Hello,
  
  I am using AR 11 version 11.2.11844.0 and PageReport which has Tablix Control.
  
  The problem was exporting pagereport (excel or pdf or even loading in viewer or preview in designer) taking several hours.

  Please see the attached sample application and run it. Notice the report displays in viewer after several hours and click on either Excel/Pdf export buttons, wait for several hours to complete the export process.
  
  Where my report has tablix control, which has one row, one column and one data field with totals. My dataset is 250k of rows.

  Change below statement (form1.cs) to use smaller dataset and notice report loads and exports without any issue.

  var reportData = GetData("TestDataset_250k_rows.xml"); // change xml file - 1k or 10k rows
  

  Also open the “testReport.rdlx” report in desinger and click on Preview. Notice preview also takes several hours to load the data.

  Can you help me how to improve Excel/PDF export using larger datasets.

  Currently i am generating the pagereport “.rdlx” dynamically (using code), setting the dataset (DataTable) at pageReport.Document.LocateDataSource += event and performing Excel/PDF/Text exports.

  Is there any performance difference loading the report in to viewer first and then export, comparing to above dynamic report building and export. Please let me know.

  Thanks,
  
  Anwar

  TablixExport.zip

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 8 January 2018, 1:43 am EST

  Hello,

  I am able to replicate the problem at our end. I have escalated this to the development team(tracking id 252459) and will revert you back once have any information from them.

  Thanks
  
  Mohit

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 17 January 2018, 5:24 am EST

  Hello,

  Sorry to mention that fixing of this issue requires a lot of time. Hence, we could not provide you hotfix for the same. Our development team are working on the issue and may be fixed in our next release, AR12 SP1. We cannot provide you estimate time on this issue. Will inform you once we have fixed this.

  Sorry for the inconvenience caused.

  Thanks,
  
  Mohit

• 

  grapecity

  • Post Options:
  • Link
    Copy

  Posted 17 January 2018, 9:27 am EST

  Hello Mohit,

  Thanks for the update. Do you have any case or tracking number for this issue. If so can you please provide me the number.

  Thanks,
  
  Anwar

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 18 January 2018, 4:23 am EST

  Hello,

  I have already given you tracking id (252459) in my first reply.

  Thanks,
  
  Mohit