Forum Discussion

2 Replies

  • In [Column1] you have data. That is a valid row. If you don't want it, filter out NULLs using a filter on [Column2]

  • Hi salim007 ,

    Here are some possible reasons:

    One possible cause is that your CSV file has a blank line at the end, which Power Query interprets as an extra row. To fix this, you can either delete the blank line from the CSV file before importing it, or filter out the blank row in Power Query after importing it.
    Another possible cause is that your CSV file has a different delimiter than the default one set in your Windows Regional settings. For example, if your CSV file uses semicolon as the delimiter, but your Windows settings use comma, then Power Query may not split the data correctly. To fix this, you can either change the delimiter in the CSV file or specify the delimiter when importing the CSV file to Power Query.
    A third possible cause is that your CSV file does not have headers in the first row, but Power Query assumes that it does. This may result in an extra row with incorrect column names. To fix this, you can either add headers to the CSV file or disable the option to use the first row as headers in Power Query.

     

    Best Regards,
    Community Support Team _ kalyj

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.