I'm importing a csv file that has a header record with some text on when it's created, and a trailer record stating the amount of rows. It imports fine in Excel 2013. PowerBI desktop could do an "untouched" text import, with all lines intact, allowing me to remove header and trailer records, and then split the column using CSV-style splitting on Comma, and keeping all data between "" (including carriage returns) in one field. Again, this worked before, and still works in Excel 2013, but today's version of PowerBI Desktop is hell-bent on interpreting the imported textfile with a delimiter, also when I change the filename to a .TXT extension (from .csv). Even if I set a custom delimiter of '&^^&#' or so, it still screws up the carriage return between "". I now work around this by importing into Excel first, but it adds manual steps to my workflow. Can you please unbreak the import features? PS I note that I have a PBIX-file that I created in the past and I refresh each week that also does this to another CSV file, and that one still works. So I conclude the wizard-to-code is broken, not the importcode itself.
... View more