When configuring a transformation command, often the wrong delimiter is set and the transformation does not execute as expected.
Not a proper CSV
If the tabular data set is not proper CSV, the OneCloud transformation command simply will not execute as OneCloud will check to see if the format is compliant with RFC 4180 before processing the input. A proper CSV:
Has data stored in plain text using a character set such as ASCII, various Unicode character sets (e.g. UTF-8), EBCDIC, or Shift JIS
Consists of records with one record per line with the records divided into fields separated by delimiters (typically a single reserved character such as a comma, semicolon, or tab; sometimes the delimiter may include optional spaces)
Has the same sequence of fields for every record
Is typically a flat-file or relational data report output
Inconsistent number of columns in each record
If records in a tabular dataset have different column counts, then OneCloud will detect that it is not a proper CSV
Different Column Counts
Combining two proper CSV tabular data sets with different column counts will simply not work and the Stack Files command will display an error.