[MGNLCTS-112] HSSFCell maximum length of contents hit during export in Excel Created: 28/Nov/19  Updated: 19/Aug/21  Resolved: 19/Aug/21

Status: Closed
Project: Content Translation Support
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Unassigned
Resolution: Workaround exists Votes: 0
Labels: y2k
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

When the upper limits of excel are reached an error is thrown.

2019-11-28 14:44:44,807 ERROR tion.ui.action.TranslationFileDownloadDialogAction: An error occurred when executing the command downloadTranslationFile from catalog translation
java.lang.IllegalArgumentException: The maximum length of cell contents (text) is 32,767 characters
at org.apache.poi.hssf.usermodel.HSSFCell.setCellValue(HSSFCell.java:574) ~[poi-3.17.jar:3.17]

Workaround:
Use another format, such as, CSV.



 Comments   
Comment by Richard Gange [ 28/Nov/19 ]

The workaround is to use another format, such as, CSV.

Or split the field so that the data does not overflow the upper limits of excel.

Generated at Mon Feb 12 00:33:21 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.