The problem is that Fetch Table only handles commas and tabs as separators. If, based on your region settings, Excel is using a comma for the decimal point, then exported CSVs will use a semicolon as the column separator.
Thanks for reporting this bug, @MartinusMagneson. We’ll modify Fetch Table (and Make Table from Text and Format Table) to correctly handle this case.
If you have the option to format the file differently when exporting from Excel, that would be one workaround. Or you could do a quick-and-dirty search-and-replace as in the attached composition (which wouldn’t correctly handle quoted/escaped separators).
In Vuo 2.4.1 we updated the Fetch Table and Make Table from Text nodes to handle CSV files with either commas or semicolons as separators. For details, see the documentation for those nodes.