Does anyone know much about CR and LF in notes for imports?
We've tried to import a CSV file from Excel with notes in the file, yet it appears that Max imports the records a line at a time. So the problem is, that if we have entries with notes that have a CR and LF in them, it drops the record to a new line, or however many it needs, and then Max sees each new line as a new record.
Is there a way around this?
I hope I'm clear enough.
Consider this example record:
name,surname, note, datenote
fred, flinstone, "Looks great CRLF
smells great CRLF
is great.",10-10-2008
john, public,hello world,10-11-2008
barney,rubble,"no notes here, only a comma in the record, so we use quotes",9-2-2008
harry,dirty,horse feed,3-3-2008
As you can see, there are only 4 records. Max sees this as 6 records.
Anyone know any work arounds without going to the XML schema?
Thanks again!
-Steve
EDIT:
We have found that removing the CR from the notes section does import it, however, when you are browsing the notes in Max, the formatting is just messed up. It would be great if we could overcome this problem.
******************************************************************************
[SOLVED FROM ANOTHER FORUM]
******************************************************************************
vr_driver:
Anyone know any work arounds without going to the XML schema?
No. CSV files cannot contain raw line-breaks within a field. Each line is a record, and the line-break (<CR><LF>
is by definition the record delimiter.Here's how I would approach the problem: I would create a note with line-breaks and then export the note from Maximizer as CSV. If Maximizer has a standard for escaping <CR><LF> I would expect to see that in the CSV export. If the CSV export has raw line-breaks in it (and hence cannot be parsed) then I would infer that the only reliable way to import notes with raw line-breaks would be via XML.
Gord Thompson
Regeneration Systems
http://www.regensys.com
Hi Gord,
Thanks for your prompt reply. After trying your suggestion and your kind note, we've decided that we have to just bite the bullet and just put the data in without CRs.
These were the results of the comma Export.
The original note: (please note that the \n\CF\LF etc, were deliberately put in there to test Max's export methods.
Testing how this
silly thing, works...
"If it Really Does, or" Doesn't \n
\CR\LDF
CRLF
Steve is cool.
Yes he is!!!!
comman
s
.
This is the result exported to a CSV file: (I have have the actual CRLF's in italic.)
"20 November 2008 11:06 AM Testing how thisCRLF
silly thing, works...CRLF
""If it Really Does, or"" Doesn't \nCRLF
\CR\LDFCRLF
CRLFCRLF
CRLF
Steve is cool.CRLF
Yes he is!!!!CRLF
CRLF
CRLF
commanCRLF
sCRLF
CRLF
."CRLF
As you can see, it can't import a file in the same format that it exports to.
Thanks again.
Steve