Unable to export reports to XLSX format
Answered
Our customer is facing issue while exporting the reports to XLSX format . When they tries to export into XLSX it throws the error 'Exception Details' . Please refer the attached screenshot.
Export to another format works fine without any error.
Yellowfin Version : 7.35
Build version :20170512
Please refer the attached logs
Regards
Pratiksha
The same question 
Hi Pratiksha,
Thanks for reaching out. Is this happening only in one report or in every report? If this is happening in only one report, what are some aspects of that report that make it differ from other reports where it's working (uses sub-queries, co-displays, etc.)?
Really though, whether it's one report or all, you're on a very old build and there have been many defects fixed related to report exports, and especially XLSX exports. As such, can you please update to the latest BMC 7.3 build and re-test? No matter the outcome, for example finding a new defect, upgrading will be a necessity anyway to resolve any issue found, so trying this in the latest build would be a necessity here to either investigate further or resolve the issue. Please let me know of your findings and whether you have any further questions.
Regards,
Mike
Hi Pratiksha,
Thanks for reaching out. Is this happening only in one report or in every report? If this is happening in only one report, what are some aspects of that report that make it differ from other reports where it's working (uses sub-queries, co-displays, etc.)?
Really though, whether it's one report or all, you're on a very old build and there have been many defects fixed related to report exports, and especially XLSX exports. As such, can you please update to the latest BMC 7.3 build and re-test? No matter the outcome, for example finding a new defect, upgrading will be a necessity anyway to resolve any issue found, so trying this in the latest build would be a necessity here to either investigate further or resolve the issue. Please let me know of your findings and whether you have any further questions.
Regards,
Mike
Hi Mike ,
Thanks for your response.
The issue is with all reports when we try to export into XLSX. Did you get anything in the logs ?
Regards
Pratiksha
Hi Mike ,
Thanks for your response.
The issue is with all reports when we try to export into XLSX. Did you get anything in the logs ?
Regards
Pratiksha
Hi Pratiksha,
The only seemingly relevant snippet from within the logs contains an ArrayIndexOutOfBounds error:
Although I'm also wondering if it could be your proxy settings causing this. In a standard Yellowfin environment, if an XLSX export failed, user's would not be redirected to a page that looks like this:
I believe every URL in SmartReporting is made to be static and referenced somewhere in the file structure, perhaps in the web.xml, though I'm not entirely sure. Whoever's responsible for the SmartReporting integration might know this. It could be worth looking into whether /MIReportOutput.i4 is included as one of the pages you're able to hit in your particular instance.
Regards,Mike
Hi Pratiksha,
The only seemingly relevant snippet from within the logs contains an ArrayIndexOutOfBounds error:
Although I'm also wondering if it could be your proxy settings causing this. In a standard Yellowfin environment, if an XLSX export failed, user's would not be redirected to a page that looks like this:
I believe every URL in SmartReporting is made to be static and referenced somewhere in the file structure, perhaps in the web.xml, though I'm not entirely sure. Whoever's responsible for the SmartReporting integration might know this. It could be worth looking into whether /MIReportOutput.i4 is included as one of the pages you're able to hit in your particular instance.
Regards,Mike
It only fails when we have format column and row size option checked, let me know if i should create a formal Ticket from BMC
It only fails when we have format column and row size option checked, let me know if i should create a formal Ticket from BMC
Hi Tarun,
It's not necessary to open a separate ticket for this. The only thing I'll need is screenshots of where and which column and row size options you're referring to so I can attempt replication.
Thanks,
Mike
Hi Tarun,
It's not necessary to open a separate ticket for this. The only thing I'll need is screenshots of where and which column and row size options you're referring to so I can attempt replication.
Thanks,
Mike
H Mike,
Even we can't reproduce it inhouse, this is specific to a customer environment , let us know if you would like to see the issue over webex
Regards,
Tarun Pandey
H Mike,
Even we can't reproduce it inhouse, this is specific to a customer environment , let us know if you would like to see the issue over webex
Regards,
Tarun Pandey
Hi Tarun,
As I'm sure you're aware, if we can't replicate the issue, our hands are pretty much tied.
Before proceeding any further though, please have the customer update to latest 7.3 build and test to see if the issue still occurs. Several defects related to exports, specifically XLSX exports, have been developed over the past 2 years.
Regards,
Mike
Hi Tarun,
As I'm sure you're aware, if we can't replicate the issue, our hands are pretty much tied.
Before proceeding any further though, please have the customer update to latest 7.3 build and test to see if the issue still occurs. Several defects related to exports, specifically XLSX exports, have been developed over the past 2 years.
Regards,
Mike
Hi Tarun,
Just wanted to check in and see whether the customer is able to update their instance and re-test any time soon or if we can close this case for now until they can go ahead and do so. Please let me know.
Thanks,
Mike
Hi Tarun,
Just wanted to check in and see whether the customer is able to update their instance and re-test any time soon or if we can close this case for now until they can go ahead and do so. Please let me know.
Thanks,
Mike
Hi Tarun,
I'm going to go ahead and mark this one as Answered for now since I haven't heard back from you, but if you have further questions or concerns on this, if you respond, it will re-open the case and put it back in my queue and I'll be happy to help.
Regards,
Mike
Hi Tarun,
I'm going to go ahead and mark this one as Answered for now since I haven't heard back from you, but if you have further questions or concerns on this, if you respond, it will re-open the case and put it back in my queue and I'll be happy to help.
Regards,
Mike
Replies have been locked on this page!