We have a synced entity based records with 13,000 and 50,000 rows respectively. However when trying to export the excel from the record list without applying filters will not do anything (not downloading even a blank excel), However in some cases applying filters download the excel but sometimes not.
I looked into tomcat-stdOut.log I see this error message.
2024-03-28 17:52:52 WARNING [http-nio-8080-exec-558] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI example.appiancloud.com/.../download-grid, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.
Not sure how to resolve this or what needs to be corrected. Any ideas or suggestions?
Discussion posts and replies are publicly visible
The log message you posted is just a warning, but no error.
Is this about one single record or multiple? You mention two different numbers.
Can you explain this filtering behaviour in more detail?
Are you sure the record(s) is/are synced? Successfully?
Multiple records are facing the same issue. The filters are user filters and yes records are synced successfully.
Do you use any custom record fields? When something works "sometimes", this smells like a timeout issue. Did you check whether the Excel export shows up in the new record query performance monitoring?
https://docs.appian.com/suite/help/24.1/monitoring_view.html#query-performance
Unfortunately environment is not upgraded to 24.1 yet.One more thing about this export we found are rich text fields. We have 2 column in the grid which uses rich text fields, if we make them as simple texts/icons exports downloads. Yes we have 3 custom records field too. Does that impact the downloads?
Since you're not on Appian 24.1 yet, some of the suggestions like leveraging features specific to that version might not be applicable. As you discovered, rich text formatting isn't well-supported by Excel exports in Appian. Removing the formatting and converting them to plain text or icons is a good workaround for successful downloads.While custom record fields themselves shouldn't directly impact downloads, the data volume within them could contribute to the issue. https://docs.appian.com/suite/help/24.1/Optimizing_Record_Lists_for_Export_to_Excel.html
hi Radhika you rich texts will not work for export the data from grid, Custom record fields data can be exported. Again if you are having large data which will be using aggregation can impact the performance
Hi Radhika ,How did you resolve this issue? We are facing the same issue in our records now. Only workaround which we see now is to create a custom process to generate this excel. But before that we need to know if this issue can be fixed.
Can you tell us the Size of the data that you are trying to export and any filters that you have or any formatted texts in it?? .If it's timeout issue just like above i suggest you to cut off the unwanted data or formatting
We found that, this issue is desktop specific. We even tried with one row and one column in grid data, but its still the same.Although this excel export is working fine in one PC but not in the other, we tried with same user login and with same filters. Not sure, if this related to the below discussion which I found relevant. Do, let me know if there any solution of this issue.community.appian.com/.../appian-ootb-record-export-to-excel-failing-with-status-code-503
Hi jagadeshkumarrk362091 I did resolve the issue. The problem was with the data. There was one column which was calculating values at run time, it was not coming directly from database. The expression to calculate that column was complex plus there was lot of records which eventually broke the export to excel. What we did is once we knew that column was culprit instead of doing calculations on load or export we created a batch process to update it nightly and save the result in database. It solved the issue and it started working fine.
But the issue was not desktop specific for us. It was not consistent because sometimes after applying the filters data the column expression rule used to skip lot of conditions and worked faster.