I just came across the fact, that the Business Central data exchange defintion dialog does NOT inlcude any option to define a text qualifier (in this case quotation marks). You'd expect, that a transformation rule (replacing the quotatio mark with nothing) applied with the field mapping should deal with it, but that's apparently not the case.
A CSV-file with a structure like "<field1>", "<field2>", ... will throw an error message upon importing, even if all columns have been defined as text type and no field mapping has been defined. That's kind of amazing, because why would a set of arbitrary characters (including quotation marks), separated by commas, not be imported just as strings?
The file won't as well be imported if the columns are set up according to content (date, number, text) and transformation rules are being used within the field mapping.
If the CSV-file on the other hand gets stripped of all quotation marks, it WILL be imported. This however is not an option, because in this file format text qualifiers ARE required: the comma sign is not only used as separator, but also as part of number formats (e.g. like in "01.01.2000", "Mobile flat rate", "77,99", "payed") - so you can't just simply remove all quotation marks without scrambling the content structure.
Can it be true, that as an end user of Business Central, you need to pay developers high hourly rates only to provide a Codeunit with the simple ability of replacing quotation marks from a text stream?
