Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Solved! Go to Solution.
This normally happens with .csv files (if it IS actually Excel it may not be applicable), PBI will usually indicate the number of columns that is in a csv in the first stage of the query, then do automatic type changing. If you stick something in the middle, then it'll move the last column out of the scope of what gets pulled in to PBI, then if it tries to change the type of the last column, it'll say it's not found.
Of course, knowing *what* error you are getting would be helpful
@joseph248
Check your Power Query steps to find out if any of the steps has Hard-Coded column names in it. If so, you need to adjust accordingly or recreate the steps so it always considers new columns.
________________________
If my answer was helpful, please consider Accept it as the solution to help the other members find it
Click on the Thumbs-Up icon if you like this reply 🙂
⭕ Subscribe and learn Power BI from these videos
⚪ Website ⚪ LinkedIn ⚪ PBI User Group
This normally happens with .csv files (if it IS actually Excel it may not be applicable), PBI will usually indicate the number of columns that is in a csv in the first stage of the query, then do automatic type changing. If you stick something in the middle, then it'll move the last column out of the scope of what gets pulled in to PBI, then if it tries to change the type of the last column, it'll say it's not found.
Of course, knowing *what* error you are getting would be helpful