Getting Vault Loader to escape line breaks in multiline field data with \r\n
Answered
When issuing a call to Retrieve Extract Results after making a call to Extract Data Files, if there are line breaks in a document Description (title__v) - or another field that allows for multiline text - those aren't escaped in the resulting CSV where the formatting is then broken. Is there a way to get vault to escape line breaks as, say, \r\n?
-
Official comment
Chris, as discussed with Product Support, your request would be considered a product enhancement and should be submitted to Veeva Connect. If you are experiencing issues registering, please work with Product Support.
CSV specifications dictate that fields that contain line breaks but must be wrapped in double quotes, but does not require those values to be escaped as /r/n. This is how Vault delivers CSVs today. Please refer to RFC 4180, Section 2.6:
https://www.rfc-editor.org/rfc/rfc4180#section-2
The issue you are experiencing is a limitation of your CSV parser. Some parser handle the line break properly, some do not. We recommend you work with your particular parsing vendor or use an alternative solution.
-
In case there was a question about it, I created a Veeva Support ticket about this but they just said that things are "working as designed" even though that means exported CSV files are essentially corrupted.
0
Please sign in to leave a comment.
Comments
2 comments