Skip to main content

Dear Calendly Support Team,

I’ve noticed that comments entered via Calendly - presumably with line breaks - are not properly handled in the exported CSV file when doing the events-export. This issue causes the resulting file to break the one-line-per-record structure, which is typically expected from a CSV export.

From my perspective, this seems like a bug in the Calendly export process. Are you aware of this issue, and is there any plan to address it? Ideally, newlines in comment fields should be ignored or handled in a way that preserves the integrity of the CSV format.

Looking forward to your feedback - thank you!

Best regards,
Johannes

Hey ​@Lido-Flight-slotbooking - Thanks for reaching out and making a report.

I’m not able to replicate this on my end, could you send me a few example screenshots of what you’re seeing? I’d like to see the comment entered on Calendly’s side, as well as what shows in the export, from there I can dig into it a bit more.

Let me know!

Hey David,

thank you for your quick response. Of course I can provide you a screenshot from one example: here you can see that the one who booked the event entered comments in 3 different lines (so 2 newlines in fact) and the csv export is taking the 2nd and 3rd line of the remark also in separate lines in the csv file. I’ve took a screenshot just of the beginning of each lines of the csv export - but here you can already see that instead of having just one line for this event we have 3 different lines for just one exported event. The 1st comment (“SR2516”) is visible at the end of the whole line, the other 2 comments are then visible in a separate line each. I hope this helps. If you have further questions or in case you need more examples, just let me know.

Thank you for your support!

Best regards,
Johannes

Screenshot from meetings page
event export

 

Reply


Need Help? Visit 'Get Help. Give Help.'
Terms & ConditionsCookie Settings