in my case, when there is a multiline field for a given type of object and it is filled (there is text separated by enter in keyboard (next line)) in objects export to csv, xlsx or exportd when the source is ExternalSystemCsv, every time i had wrong data in such files comes out because that enter in that field moving to csv or excel and no program can handle it.
i have 8 objects in this objects of type and i filled object similar like that:
and list of objects:
when i click export to csv or xslx i get this
i have 8 objects but in many entries
i should get csv, xlsx, ExternalSystemCsv for 8 objects in which i should saw only 8 entries and header so i should saw max 9 entries but there are many more.
You should think about how to fix enter in keyboard (next line) in filed multiline (textarea) when export to csv/xlsx.
The same situation is when i have created job in exportd and destination is ExternalSystemCsv.
Maybe You should think about change next line sign to example for 3-5 spaces or any different sign what You want?
I think You should fast fix that bug because that is important function and don’t work ok.
As long as you managed to deal with the new lines (enter) for the multiline (textarea) field in the list of items, as you can see on one of the screens in this topic, you forgot about the exports to csv and xlsx.
I only tested these functions, so I can talk about them. Perhaps errors with lines also appear in other cases. This has to be checked