When exporting TRIRIGA records that contain text fields with carriage returns and line feeds, these fields will have extra spacing between the rows when viewed in the Excel spreadsheet.
The issue is that Excel treats CR+LF (\r\n\) as two separate line feeds. Some operating systems such as Windows use \r\n to represent a carriage return. The fix is to detect the existence of \r\n in a text string, and treat it as single line feed (\n) that Excel recognizes.
Moving forward, we resolved a query export-to-Excel issue, where each carriage return in an exported text field value was appearing in the Excel cell value as two new lines. The fix ensures that Excel cell values display each carriage return in a text field value as a single new line.
[Admin: To see other related posts, use the Excel tag.]