Excel export issue

Posted by: amirgeri on 3 August 2017, 3:18 pm EST

  • Posted 3 August 2017, 3:18 pm EST

    I've been having problem exporting my report to xls from the web viewer.



    Attached is the rdlx file, pdf export and excel export.



    The rdl is generated at runtime and the data is given to the report via the resource locator.



    As you can see, the excel doesn't have the generated data...



    Amir.
    2011/11/Excel Problem.rar
  • Replied 3 August 2017, 3:18 pm EST

    Hello,

    The excel comes out fine at my end, when I test the RDLX with some sample data and the latest public build. If you are using some older build, then please upgrade to the latest one from this link.Also, i am attaching the RDLX with the sample data that comes out fine in Excel at my end. Please try running it at your end and check for results. If the issue is not observable in this RDLX but when running the RDLX at your end, if possible please send a segment of the data(in xml etc) for me to reproduce the issue.

    Regards,
    Prantik

    2011/11/SummaryEvaluationsScores.rdlx
  • Replied 3 August 2017, 3:18 pm EST

    Hello,

    There are some overlapping dataregions on the report. Please make sure that there are no overlapping dataregions. If you open the RDLX in the designer, it will give you the error message regarding the overlapping dataregions. Further, please upgrade to the latest build of DataDynamics Reports that we have recently released and check if the issue still exists.

    Regards,
    Prantik
  • Replied 3 August 2017, 3:18 pm EST

    I've added a minimal gap between data regions, updated the binaries and even stripped the report to a simple table and still the excel won't export properly.



    I've attached the new files.
    2011/11/ExcelExportIssue.rar
  • Replied 3 August 2017, 3:18 pm EST

    I've attached xml with the data.

    Be advised that I'm setting the data via the locate data source event.

    And I've already updated my DDR release.
    2011/11/ExcelExportIssue-2.rar
  • Replied 3 August 2017, 3:18 pm EST

    Amir,

    Unfortunately, I am still unable to reproduce the issue with your data. Please check the attached application that consumes the RDLX and the relevant data(I have removed the datasets not required by the tables therein). At my end the report is exported to Excel fine. Could you please modify the same to reproduce the behavior?

    Regards,
    Prantik

    2011/11/ExportToExcel.zip
  • Replied 3 August 2017, 3:18 pm EST

    However, as an immediate workaround, you could save the reportdefinition created to a file in the server ->create a new reportdefinition out of it and use it in the reportruntime to be consumed in the WebReportViewer. This approach works fine for me.

    Prantik
  • Replied 3 August 2017, 3:18 pm EST

    Further,

    I am unable to figure the code by which you assign the images to the first detail column in the Table, which seems to be striped, when I save it to a File. Could you please shed some light on how exactly you are pulling the images onto the first cell.

    Regards,
    Prantik
  • Replied 3 August 2017, 3:18 pm EST

    Thank you for your replies, I'm looking forward for the definite answer.



    As for the images, in order to decide which image to add to the column, I'm testing the value in the column and put in the image as a "state" image - Red/Green/Yellow.



    The ExpressionInfo of the image is as follows:

    =Switch(Fields!PrevGradeDiff.Value = -0.5 and Fields!PrevGradeDiff.Value 0.5, "Positive")



    The image is not what makes the export fail, I've attached a modified example that does not use images and still doesn't export to excel. Maybe its the rectangle?



    As for the work around:

    unfortunately, when I do save the original report to rdlx, the images are not written to the file, and that breaks an important functionality of mine.



    In any case, saving file into the file system in web application is pretty much a bad practice but as I've said before it won't fix my problems anyway...



    Amir
    2011/11/ExportToExcel-2.rar
  • Replied 3 August 2017, 3:18 pm EST

    I've modified your sample to reproduce the problem.

    The main change that help reproduce it is to create the ReportDefinition in memory and not from file.

    Attached is the modified project.
    2011/11/ExportToExcel.rar
  • Replied 3 August 2017, 3:18 pm EST

    Amir,

    I am able to observe the issue. But I will need some time to analyze it as it involves a lot of custom code that you have used to generate the reports.

    Regards,
    Prantik
  • Replied 3 August 2017, 3:18 pm EST

    Hello,

    I am able to observe the issue in any reports created at runtime and having a Table reportitem within it. I believe you too do not observe this issue in reports created at runtime and not having a Table reportitem. I have entered Case 157460 for our developers to address this.

    Regards,
    Prantik
  • Replied 3 August 2017, 3:18 pm EST

    Hello Amir,

    Unfortunately,I cannot provide an ETA on Case 157460. Regarding the issue of the images not getting rendered when the rdlx is saved to the Server's physical memory, I was unable to find the code where you have set the ExpressionInfo as mentioned in your earlier post. Does this come from any of the plug in dlls that you have created?

    Regards,
    Prantik
  • Replied 3 August 2017, 3:18 pm EST

    Any ETA on the solution?
  • Replied 3 August 2017, 3:18 pm EST

    Yes. it's from the dll Top.Reporting.Plugins.DataDynamics.

    However, I believe the problem persists even with simpler ExpressionInfo.



    Amir.
  • Replied 3 August 2017, 3:18 pm EST

    Amir,

    Images added to a report created at runtime are displayed fine when I save the report to the file system and load it back.Please check the attached sample.Could you please change this sample to demonstrate how in your code are you adding the images.

    Regards,
    Prantik

    2011/11/DDRCreatedRuntimeWithImages.zip
  • Replied 3 August 2017, 3:18 pm EST

    What about the fact that rdls written from the definition are missing the images in the report?
  • Replied 3 August 2017, 3:18 pm EST

    Hello,

    The Case 157460 is still open. Unfortunately, there is no  ETA on the Case.

    Regards,
    Prantik
  • Replied 3 August 2017, 3:18 pm EST

    Is there any news on the matter? We are approaching development and this is a crucial functionality!
Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels