Forum Discussion
Super UserCSV to table not working from Lakehouse File section
The encoding is UTF-8, very standard. I guess there might me another issue which is just not known currently. For now as non of the mentioned options actually solved the issue I see the workaround using the inport directly in Power BI as only solution.
Thanks and best regards.
Super Usernielsvdc excelent idea. In the meantime I also tried to take the CSV in a Dataflow but not from the Lakehouse rather then from my local file share. Also this way works.
So it seems as only the way of getting the CSV located in the Lakehouse Files section does not work in the same way as with Power Query either in PBI Desktop or Dataflow.
If anyone has an idea why this is the case, feel free to comment.
Thanks!
Super UserWhen you import a CSV file using a Dataflow from a lakehouse files folder, dataflow will generate the following steps:
- Source > Authenticate to Fabric Lakehouses
- Navigation > Filter workspace
- Navigation 1 > Filter lakehouse ID
- Navigation 2 > Filter Files folder
- Navigation 3 > Filter CSV file
- Imported CSV > Import the CSV document using Csv.Document function
When step 6 is not created automatically, then probably the CSV file has different encoding or delimiter than the default (encoding: UTF-8, delimiter: ",") and dataflow does not recognize one of them to be sure to make the step automatically.
In these cases you can create step 6 manually by using the code:
Csv.Document(#"Navigation 3", [Delimiter = ",", Encoding = 65001, QuoteStyle = QuoteStyle.None])You need to change the delimiter, encoding and quotestyle manually to meet the file's specification.
Check the possible options for Csv.Document parameters.
Hope this helps. If so, please give a Kudos 👍 or mark as Accepted Solution ✔️.