Forum Discussion
Power BI not loading the data in certain tables
You would have to modify the CSVDecode step.
But - all of these steps could be part of the Power Query ETL process if you want. You can use things like
try ... otherwise ...
to ingest the raw CSV either with commas or with tabs and then you can delete/discard the columns with the PII.
Super Userwhen you visually inspect these CSV files do you see a difference?
Mmm yes, there is a difference. I download the file daily using Power Automate to create the csv table. Since the file is originally tab separated instead of comma separated, I have an action that replaces commas with tab to generate and it seems that for some reason, after that date, it started changing the format. The correct format looks like this:
And the incorrect one is putting everything into columns:
Perhaps I should take this query to the Power Automate forum instead, as based on this the problem is not the power BI.
- lbendlin
You can use Power Query to sense if the file is tab or comma separated, and then ingest it accordingly.
Where do you download the file from?
Since the file is originally tab separated instead of comma separated, I have an action that replaces commas with tab to generateThat's not recommended. Better to to leave the raw files as is and handle the changes in a tool that is a bit more robust than Power Automate.
Ohh I did not know that was possible from Power query. The original file is downloaded from the company website, but then some columns need to be removed for data privacy reasons and we need to keep the rest of the columns. Most columns will include dates or binary information to determine if certain data is available in the file or not. In Power Automate I was able to do that, but when I try to generate the CSV file for Power Bi to consume it, it was giving me issues for being a tab separated file instead of a comma separated file, because I was using the Create CSV table action in Power Automate. That's why I needed to change the delimiter, but now I don't know why it started changing the format of the file. What other tool would you suggest to do this instead? This is the flow I use to generate the file:
- lbendlin
You would have to modify the CSVDecode step.
But - all of these steps could be part of the Power Query ETL process if you want. You can use things like
try ... otherwise ...
to ingest the raw CSV either with commas or with tabs and then you can delete/discard the columns with the PII.