Forum Discussion
New data file failing in query import
Hey, jillmhendrix I would drop the automatic combiner and write one yourself, it's way less messy and you have more control around it + you learn something new, it's not very hard.
You can just click steps for one of your files, remove steps with navigation and keep first step as the binary content, wrap the whole thing as function and that's it.
Then in your actual Query, do the navigation, get your files, and add new column where you invoke the function with the content (or transform existing content column).
Here's blog about it:
https://www.vojtechsima.com/post/combine-files-quickly-in-power-query
If it's a SharePoint, use a connector like this:
= SharePoint.Contents("https://tenant.sharepoint.com/sites/siteName", [ApiVersion=15])
Thanks - I do find the multiple queries confusing so I will try this. Since I'll have to be rewriting things anyway, do you recommend switching the file imports from .xlsx to .csv at the same time? I have the ability to export as .csv but had been using .xlsx since easier for me to open the files and double-check things in them.
- vojtechsima6 months ago
Super User
Hey, jillmhendrix, it depends on the size of your data, but it doesn't really matter.
CSVs are more universal; I would stick with them, but if you have already .xlsx, it's okay.