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 from the meetings page to see what has been entered:

Meetings page

  In addition, I’ve took a screenshot from the beginning of each lines of the csv export - 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:

event export - beginning of the lines

Another screenshot I’ve took from the end of the line of the exported event where you can see the 2 empty lines below from the 2nd and 3rd line of the comments:

event export - end of the lines

Summary: 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


Understood - Thanks for sending all of this over for more context.

Just to confirm, do you see this right after you download the file? Or does it only do this after you import it into Excel/Google Sheets. I still can’t quite seem to reproduce it, but I’ll keep digging to see what else might be going on.

For example, this is what I’m seeing when I test this, which should be intended:
 

Let me know! 


It shows when opening the file right after the download via Excel. But also when I open it using Windows Editor it’s showing the line breaks:
 

 


Got it, thank you for checking!

Last thing I’d like to check - Would you be able to to pull this report into Google Sheets and see if the same problem occurs? If you don’t have a google account thats fine - I’ll just need to dig more on my end. 

Let me know! Looking forward to hearing back.


Hi ​@Lido-Flight-slotbooking - Did some more researching here to try and find if anyone else has experienced this before.

I was able to find one user who ran into this with excel, but importing the file into Google Sheets did allow it to display correctly for them. I did some more digging and found a helpful article about Microsoft Excel and CSV files. In some cases you may need to edit your Excel settings in order for the CSV file to be read correctly. I’d recommend checking out this guide here to adjust your Excel settings, these steps have solved it for a few users before.

Let me know if this works!


Hi David,

thank you very much for your research and support! Unfortunately, it doesn’t help me. The point is that I’m not trying to read the file using Excel but rather move the csv file to a script that is parsing the data. And due to the fact that obviously some newline is taken over from the comment line is part of the file, the script doesn’t consider everything after the newline as this is not according to csv definition. I assume it’s an issue with Calendly export function which probably should eliminate newlines in such cases, but I’m just guessing. Do you see an option to report it to a developer being responsible for the csv export function to check that? Thank you very much again!

Best regards,
Johannes


Hi Johannes. 

I’ll reach out to the team today so they can dig into it more. Once I hear anything I’ll get back with you!

If you have any questions in the meantime, let me know!