You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure exactly how to explain this, but some fields (usually the large comment field) allows user entered data to mess up the system of comma/quote separation of fields, so that when data is exported and opened in Excel or Open Office Calc, some of the rows are messed up. It also looks like sometimes my comment field has quotations around it, but sometimes it does not. Perhaps a problem with \out chars like single or double quotes? I can supply an exported example if necessary, though it contains data I would not want publicly visible.
Just an update. This bug seems to be slightly different in latest versions (ft 2.1.5 and export manager 2.1).
When I export an Excel version, the file opens fine in Excel, but when I export a csv file, a textarea data field seems to break the line and thus mess up the csv file. Also, if I save the exported Excel version as a csv file, the new csv file also has the broken line problem, even though the Excel file displays ok in Excel (i.e. no broken line.)
Seems like textarea fields are carrying along a carriage return, perhaps? I tried adding wrap=virtual and deleting all the spaces in the textarea html, but that doesn't seem to make a difference.
.ID,Last Name,First Name,Email,Phone,Org,Category,Address,City,State,Province,Country,Zip,DL Interest,Find Us,Support nit removal?,Prevention Program,Failed Treatment,Caused Illness,Comments,Date,Last modified,IP Address
24203,Moore,Andy,[email protected],phone,Moorezilla,Education,5 Linden,Peabody,Massachusetts,,United States of America,01960,"No Nit Policy, Other",Internet Search,yes,no,yes,n/a, test
,2011-10-27 12:28 PM,2011-10-27 12:46 PM,71.233.45.129
Not sure if this will translate right. Problem seems to occur right before date field... right after textarea field for Comments.
The text was updated successfully, but these errors were encountered:
Not sure exactly how to explain this, but some fields (usually the large comment field) allows user entered data to mess up the system of comma/quote separation of fields, so that when data is exported and opened in Excel or Open Office Calc, some of the rows are messed up. It also looks like sometimes my comment field has quotations around it, but sometimes it does not. Perhaps a problem with \out chars like single or double quotes? I can supply an exported example if necessary, though it contains data I would not want publicly visible.
Just an update. This bug seems to be slightly different in latest versions (ft 2.1.5 and export manager 2.1).
When I export an Excel version, the file opens fine in Excel, but when I export a csv file, a textarea data field seems to break the line and thus mess up the csv file. Also, if I save the exported Excel version as a csv file, the new csv file also has the broken line problem, even though the Excel file displays ok in Excel (i.e. no broken line.)
Seems like textarea fields are carrying along a carriage return, perhaps? I tried adding wrap=virtual and deleting all the spaces in the textarea html, but that doesn't seem to make a difference.
.ID,Last Name,First Name,Email,Phone,Org,Category,Address,City,State,Province,Country,Zip,DL Interest,Find Us,Support nit removal?,Prevention Program,Failed Treatment,Caused Illness,Comments,Date,Last modified,IP Address
24203,Moore,Andy,[email protected],phone,Moorezilla,Education,5 Linden,Peabody,Massachusetts,,United States of America,01960,"No Nit Policy, Other",Internet Search,yes,no,yes,n/a, test
,2011-10-27 12:28 PM,2011-10-27 12:46 PM,71.233.45.129
Not sure if this will translate right. Problem seems to occur right before date field... right after textarea field for Comments.
The text was updated successfully, but these errors were encountered: