Thank you for your post!
I will send a report to Testing and Development for feedback on your findings. Could you let me know in what ways this is affecting your use?
Windows based third-party applications which require a CRLF don't recognize the record breaks (instead of just a CR, which is the Mac standard and what Cloud server appears to export).
Since the Cloud server is Linux, I would posit that the export is pushing just the LF (line feed) - the default "end-of-line" for UNIX, rather than the CR (carriage return of MacOs)
and not the needed CRLF (on Windows)
Thanks Beverly. It actually appears as though it's exporting with just a CR (I guess the cloud/Linux default is the same as Mac) and no LF which is why windows applications aren't recognizing the breaks.
I've found a workaround using a global field and scripting a loop through records and concatenating a text string with a CRLF in between then just exporting the single global field as text with a .csv extension. This is more consuming on the server but appears to work fine for now. While it isn't the case for me, it'll mess up any windows users on pro as the same script will export in two different manner on webdirect vs pro.