• State Verified Answer
  • +4 person also asked this people also asked this
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 9 subscribers
  • Views 12615 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Plug-Ins

Excel Tools Data Subset Export Returning HTTP 500

Kyle Jorgensen

The download links in several reports in our production environment have started returning HTTP 500 errors when clicked. This seems to be occurring for all users and is not isolated to a single report.

The download link is driven by the Excel Tools data subset export. The related export process is completing successfully and I am not seeing any errors in the process, but when I look in the logs I see this whenever someone tries to use the link:

17:38:10,332 INFO  [stdout] (ajp-/0.0.0.0:8009-32) 2017-08-15 17:38:10,332 [ajp-/0.0.0.0:8009-32] ERROR com.appiancorp.ap2.PortalResponse - Error: 500

17:38:43,719 INFO  [stdout] (ajp-/0.0.0.0:8009-32) 2017-08-15 17:38:43,719 [ajp-/0.0.0.0:8009-32] ERROR com.appiancorp.ps.exceltools.servlet.ExportDataSubsetToExcelFromProcessServlet - Expected 898 but found 97

17:38:43,719 INFO  [stdout] (ajp-/0.0.0.0:8009-32) java.security.InvalidParameterException: Expected 898 but found 97

I am not sure how to decode these errors, so any help in this area would be appreciated.

  Discussion posts and replies are publicly visible

Parents
  • 0
    A Score Level 2
    This might happen if ExportableDataSet is not getting a datasubset as its input. This can happen for instances such as when the filters applied on the query entity makes it return empty dataset. Then in such cases, you have to create a structure of the datasubset like todatasubset(type!CDT(field1: null, field2: null), a!pagingInfo) and then pass it to Exportabledatasubset. Usually the 500 response error happens for such cases where either the datasubset is not returned properly or one of the field names is not there.
Reply
  • 0
    A Score Level 2
    This might happen if ExportableDataSet is not getting a datasubset as its input. This can happen for instances such as when the filters applied on the query entity makes it return empty dataset. Then in such cases, you have to create a structure of the datasubset like todatasubset(type!CDT(field1: null, field2: null), a!pagingInfo) and then pass it to Exportabledatasubset. Usually the 500 response error happens for such cases where either the datasubset is not returned properly or one of the field names is not there.
Children
No Data

© 2024 Appian. All rights reserved.