locked
Bug introduced in PQ 2.24 with Csv.Document for files with LF carriage control RRS feed

  • Question

  • This is related to my prior post, "Bug in Csv.Document introduced in Power Query 2-22".  That specific issue has been fixed in the 2.24, 7/14/15 release of Power Query.  Unfortunately, with it a new bug/regression has been introduced in 2.24.

    In 2.24 with Csv.Document and Delimiter=",", line-feed (LF alone as opposed to CR/LF) is no longer recognized as end-of-line.  This results in Power Query attempting to read the entire file as one record (one line, many, many columns).  For large files, Power Query will seemingly hang when trying to open the CSV and eventually error out or display a message that the display value is too complex.

    You can easily create a test file in Notepad++ and change the carriage control with Edit -> EOL Conversion -> UNIX/OSX Format

    "1","one","two","three"
    "2","one","two","three"
    "3","one","two","three,"
    "4","one","two","three"
    "5","one","two","three"
    "6","one","two","three"

    My test file results in the following:

    Column1 Column2 Column3 Column4 Column5 Column6 Column7 Column8 Column9 Column10 Column11 Column12 Column13 Column14 Column15 Column16 Column17 Column18 Column19
    1 one two three "2" one two three "3" one two, three, "4" one two three "5" one two three "6" one two three

    CsvStyle=CsvStyle.QuoteAlways will correct this behavior, but there is no method of adding this using the UI.

    Dale


    • Edited by Dale Hohm Wednesday, July 22, 2015 1:54 PM
    Wednesday, July 22, 2015 1:47 PM

Answers

  • Thanks for identifying the workaround. This has already been fixed, and the fix will be in the next release.
    • Proposed as answer by Curt Hagenlocher Thursday, July 23, 2015 6:42 PM
    • Marked as answer by Dale Hohm Thursday, July 23, 2015 7:32 PM
    Thursday, July 23, 2015 6:42 PM

All replies

  • Thanks for identifying the workaround. This has already been fixed, and the fix will be in the next release.
    • Proposed as answer by Curt Hagenlocher Thursday, July 23, 2015 6:42 PM
    • Marked as answer by Dale Hohm Thursday, July 23, 2015 7:32 PM
    Thursday, July 23, 2015 6:42 PM
  • I can confirm that this problem has been addressed in the Aug-14-15, 2.25 release of Power Query.

    Dale

    Tuesday, August 18, 2015 4:00 PM