FlexPreview Export to Excel error maximum number of rows exceeded

Posted by: chn on 11 November 2019, 3:16 pm EST

    • Post Options:
    • Link

    Posted 11 November 2019, 3:16 pm EST

    Hi,

    I am using C1FlexViewer (4.0.20192.375) to display my report.

    The report approximately 1600 pages (almost 70.000 rows), when I click ‘export to a file’ button then select save as type ‘Open XML Excel (*.xlsx)’ then save. When exporting, the C1flexViewer status show ‘[ERROR]: Maximum number of rows exceeded (65,536).’

    Any solution?

    Thanks

  • Posted 12 November 2019, 5:49 pm EST

    Hello,

    We are investigating on this.

    For a time being please share a GIF with the error message that you are getting at your end and also share a report file with dummy data in which you are facing the issue. It will help us to investigate on this in a better way.

    Regards,

    Prabhat Sharma.

  • Posted 13 November 2019, 4:34 am EST

    Hi,

    This is the error displayed in C1FlexViewer status:

    Thanks

  • Posted 13 November 2019, 8:22 pm EST

    Hello,

    This error generally comes when you export to Excel in .xls format with more than 65,536 rows but as you are export to ‘Open XML Excel (*.xlsx)’ format, it is very strange of this error to occur.

    We understand that you are facing issue at your end so can you please share a Video file of running your application so that we can follow the same steps to replicate the issue at our end and thus forward this to the developers.

    Regards,

    Prabhat Sharma.

  • Posted 15 November 2019, 4:02 pm EST

    Hi,

    Here is the video, hope it clear enough to show the problem:

    Thanks,

  • Posted 17 November 2019, 6:19 pm EST

    Hello,

    Thank you so much for the GIF.

    We have escalated the case to the developers, will let you know once we get any updates on this. [Internal Tracking Id : 407620]

    Regards,

    Prabhat Sharma.

  • Posted 1 January 2020, 10:28 pm EST

    Hi,

    I am having the same issue. Has this been resolved?

    Thanks,

    Paul

  • Posted 2 January 2020, 2:20 pm EST

    Hello,

    We are asking the developers for the updates, will let you know soon.

    Regards,

    Prabhat Sharma.

  • Posted 2 January 2020, 8:58 pm EST

    Hello,

    We have got the response from the developers and as per them, this issue will get fixed in 2020V1 release.

    Regards,

    Prabhat Sharma.

  • Posted 17 March 2020, 9:57 pm EST

    Hi,

    I am glad to inform you that the issue has been fixed in the latest build (i.e. 2020v1). You can get it from the link below:

    http://prerelease.componentone.com/dotnet452/c1winform/2020-t1/C1WinForms-452_4.5.20201.416.zip

    Thanks,

    Pragati

Need extra support?

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

Learn More

Forum Channels