Author: Jonathan Rivera
Date: February 14, 2024
Audience: Everyone
Environmental details: Self-hosted or Cloud
Summary:
After exporting a report from Trace View, opening the CSV in Excel has broken formatting. This will likely show up as large gaps between rows with seemingly random words being cut off.
Solution:
- Check how many characters are in the cell that precedes the broken formatting.
- If it is at (or close to) 32,767 characters, that cell is too large for Excel to handle.
- Exclude columns from Trace View that are too large. (This will typically be large text fields, such as the Description field.)
Cause:
Excel's character limit for a single cell is 32,767 characters. The formatting in Excel will break right around where a large cell hits that limit.
Prevention:
Do not include large fields in the Trace View columns when exporting.
Related Articles, Work orders, Zendesk tickets, Defects, etc.
Additional Information/Metadata:
- Report
- Trace View
Feedback: Please leave feedback in the comments below.
Comments
1 comment
The problem is not the character count; the problem is that the csv export is not capable of handling the html code export from Jama.
The data in Jama is stored as html, for example:
<p> Here is a requirement that shall meet the following list: </p>
<ol>
<li> First List Item </li>
<li> Second List Item </li>
</ol>
When in Jama, this would show up as the sentence and then numbers (1, 2). But when exported into CSV from the Trace View, it exports as just spaces and new lines. So you end up having the Trace View with formatting that does not match what is in Jama.
There should be an option to export into excel with the full html code, this way we can clean up the html and have it provide the accurate formatting.
Please sign in to leave a comment.