Power BI’s Combine files workflow (from a folder) is supposed to standardize multiple files into one table using Power Query. When it stops working, you usually don’t have a “Power BI bug”—you have inconsistent file structure, a bad sample, or a query that Power BI generated incorrectly.
This guide focuses on one practical goal: get Combine Files working again quickly. You’ll use three fixes that address the most common causes—schema mismatches, incorrect transforms, and a broken/fragile combine query—plus a deeper troubleshooting checklist and FAQs.
As an Amazon Associate I earn from qualifying purchases.
What Combine Files in Power BI Actually Does (and why it breaks)
When you choose Combine files, Power BI scans a folder, picks a sample file, and generates a Power Query (.query) function that loads each file and applies a transform to produce a consistent output table. If anything about the files or the sample-driven transform is inconsistent (column names, types, delimiters, sheet names, row structure), refresh can fail or produce unexpected results.
Typical symptoms include: Combine Files silently produces the wrong columns, errors during preview/refresh, or the resulting query changes behavior after you add or rename files.
#1 Best Overall
Prerequisites before you troubleshoot
- Power BI Desktop with Get Data > Folder (or the file-folder workflow) available.
- A folder containing the files you’re combining (not a one-off file view).
- At least 2 files that should share the same structure (same columns, same header row, same delimiter/sheet/table).
- Enough detail to reproduce: the exact error message, and whether the failure happens at preview, during transform, or only on refresh.
If the feature works for one folder but fails for another, treat that as a strong signal that your files’ schema (not Power BI) is the root cause.
3 Quick Ways to Fix Power BI Combine Files Not Working
Use these in order. Each one targets a common failure mode and tends to fix 80%+ of cases fast.
1) Make file schemas match (names, data types, headers, and delimiters)
Combine Files assumes every file can be transformed into the same output schema. The #1 reason it breaks is that one (or a few) files differ from the rest.
Start by checking these areas in every file you’re combining:
- Header row alignment: CSVs should start data immediately after the header row; Excel should use the same sheet/table and header placement.
- Column names: even minor differences like
Customer IDvsCustomerIDorDatevsDATEcan derail the transform. - Data types: if one file has numbers stored as text (or dates stored as text), the type changes can cause step errors.
- Delimiter/encoding (CSV): one file using semicolons
;while others use commas,will break parsing.
Concrete example: If you combine CSVs and one file uses ; instead of ,, Power BI may load it as a single column, and later steps referencing expected columns will fail.
What to do: edit the “odd” file(s) so headers and structure exactly match. Then re-run Combine Files.
2) Fix the transform step Power BI guesses wrong (Transform sample, then set parameters)
Power BI generates steps based on a sample file. If the sample is unusual—extra blank rows, different sheet name, different column order—your combine query bakes in the wrong logic.
Step-by-step (Power Query):
- In Power BI Desktop, go to Transform data to open Power Query Editor.
- Locate the query created for the folder combine (often a function plus a main query). Look for steps that reference sample transformation (commonly steps like promoting headers, type changes, removing columns/rows).
- Right-click your folder combine function/query and choose View (if prompted) to inspect the function logic.
- In the function/query, set the correct parsing and transformation for your files. For CSVs, confirm delimiter/encoding in the source step; for Excel, confirm the correct sheet or table name.
- Use Transform steps explicitly:
- Promote headers only if every file truly has headers in the same row.
- Set column types consistently (e.g., Date = Date type, Amount = Decimal Number) after parsing is correct.
- Close & Apply to reload and test preview/refresh.
Common “guess wrong” scenario: One Excel file uses a different tab name (e.g., Sales vs sales) and Power BI hardcodes the tab from the sample. When it hits other files, you get an error or blank tables.
3) Rebuild the combine query cleanly (new sample + consistent folder path)
If your combine query has grown brittle (accidental steps, partial fixes, or inconsistent sampling), rebuilding it from scratch is often the fastest “real fix.”
Step-by-step rebuild:
- Pick a representative sample file that matches the majority schema and is free of anomalies.
- In Power BI Desktop, go to Home > Get Data > Folder.
- Select the folder path containing the files. Ensure the same folder (not a shortcut/redirected path) is used each time.
- When the files load, choose Combine (or follow the wizard that creates the Combine Files query).
- In Power Query
In Power Query, select the correct table/sheet after expansion, then apply the same transforms (headers promoted, types set, columns filtered) you verified in your sample file.
After that, confirm the output table shape is identical for the sample and for at least one “different” file (the one you suspected was causing issues). Once the query is stable with the new sample, refresh the model.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.Pro tip: When you rebuild, don’t keep old custom steps that “sort of worked.” In combine scenarios, small differences can create hard-to-find failures later.
Rank #3
Other fixes that solve common “Combine Files” failures
Confirm file access and folder consistency
Sometimes Combine Files fails for reasons that have nothing to do with column structure. Power BI may be reading from a folder you can view but not fully access (common with OneDrive/SharePoint permissions), or the folder path you selected includes redirects that behave differently on refresh.
- Check permissions: make sure the account running the refresh (your Desktop session or your service credentials) has read access to every file in the folder.
- Use a stable folder path: avoid selecting a view that changes (for example, a “recent” folder, or a redirected shortcut path).
- Validate file availability: remove temporary files, half-uploaded files, or files being written during refresh.
If the error appears only in the Power BI Service (not locally), permission and path stability are your first suspects.
Handle hidden files and extra sheets/tables
Power BI’s folder combiner usually targets “files in the folder,” not “just the files you intended.” Hidden files (or extra Excel tabs) can break the transform.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.Look out for:
- Hidden/temporary files: CSVs like
~$filename.csv(or Excel temp files) can appear and fail parsing. - Excel with multiple sheets/tables: if some files use a different sheet name, you need to filter to the right one.
- Different table names (Excel structured tables): the combine function may expand the wrong object unless you standardize tab/table naming.
What to do: in Power Query, filter the folder list by file extension and exclude known temp/hidden patterns before expansion. Then explicitly choose the correct sheet/table when expanding.
Deal with blank or malformed rows
Even when headers and columns match, one bad row can derail type conversion. This is especially common when a “mostly numeric” column contains a stray text value, or a date column contains blanks in some files.
How to spot it fast: sort/filter in Power Query after the combine step and look for rows that fail type conversion or appear as null/blank unexpectedly.
Common fixes:
- Trim/clean text fields to remove non-printing characters.
- Use robust type handling: convert with care (for example, parse dates and allow blanks instead of forcing every value).
- Filter out malformed rows before applying strict type transformations.
If your issue is “refresh breaks but preview works,” check for rows that only appear after all files are loaded—preview sometimes samples a subset.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.Performance and refresh gotchas
Combine Files can also “fail” in practical terms when it’s slow, times out, or refreshes inconsistently—especially with large folders.
- Large folders / many files: consider reducing scope (only load files matching a date range or naming convention).
- Expensive transformations: do light filters earlier in the query to reduce the amount of data processed.
- Avoid unnecessary re-typing: set types once after parsing, not repeatedly across steps.
- Incremental refresh (if applicable): helps a lot when you’re adding new files regularly.
Bottom line: if your combine query is doing heavy work before it filters, refresh can time out or hit memory limits—leading to errors that look like “Combine Files not working.”
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Comparisons: Combine Files vs Power Query settings you can control
One reason this breaks often is that Combine Files is an automation wizard: it guesses based on a sample and generates the “function + transform” structure for you. After that, it’s still Power Query under the hood—so anything you can control in Power Query (headers, types, parsing, sheet selection, row filtering) can and should be made explicit.
If Combine Files is unreliable in your environment, you can sometimes get more stability by taking over: use Power Query to list files, filter what you want, and explicitly invoke the right parsing logic per file type—rather than relying entirely on the wizard’s sample-driven assumptions.
Recommended Free Tools
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.Troubleshooting checklist (fast diagnosis)
- Does one specific file cause the failure? Temporarily exclude files until the error stops—then you’ve found the culprit’s structural mismatch.
- Are headers identical? Exact column names, same header row, same spacing/underscore/casing.
- Are types consistent? Date/number columns must parse the same way across files.
- Is delimiter/sheet/table selection consistent? CSV delimiter and Excel sheet/table names must match what the query expects.
- Are temp/hidden files present? Filter the folder list to exclude non-data files.
- Does preview succeed but refresh fail? Look for blank/malformed rows and permissions/path differences.
When you follow that order, you’ll usually find the root cause quickly—without rebuilding everything unnecessarily.
Best Value
FAQs
Why does Combine Files work in one folder but not another?
Because the wizard’s sample-driven transform only matches what it sees. If the other folder has different naming, sheet/table selection, delimiters, or even a single “odd” file with a different schema, Combine Files can break.
Can I change which file Power BI uses as the sample?
Not directly with a simple checkbox in all cases, but you can control it by rebuilding the combine query using a folder that includes a representative “good” sample, or by restructuring your approach so the transforms are explicit rather than sample-dependent.
What’s the most common Combine Files failure?
A schema mismatch—usually a difference in column names, types, delimiter/encoding (for CSV), or Excel sheet/table name. The second most common is a fragile query generated from a “bad” sample.
Free tools Windows power users keep installed
One-click scans. No signup required.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.Bottom Line
Power BI’s Combine Files isn’t “randomly broken”—it’s faithfully applying a transform that was generated from a sample file. When your files aren’t truly identical in structure (or when hidden/temp files slip in), the combine logic can’t reliably produce one consistent table.
If you start with schema matching, then fix the transform steps, and finally rebuild the combine query using a clean sample + consistent folder path, you’ll fix the majority of “Combine Files not working” issues quickly—and you’ll end up with a query that’s much easier to maintain.
Quick Recap
SaleBestseller No. 1SaleBestseller No. 3SaleBestseller No. 4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
