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!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
I'm importing an Excel file which contains a table from SharePoint into a dataflow. I'm testing each query and I'm able to see the data at each step. However, when I Save and Copy. Power Query adds an extra step in the data load query and the subsequent queries fail to analyze and the data flow does not save to the workspace.
The additional step is as follows:
Solved! Go to Solution.
I resolved the issue by collapsing two queries into one. Placing the Navigation step (query 2) after the Imported Excel step (query 1) prevented Power Query from generating the Table.RemoveColumns step in the newly combined query.
I'll chalk it up to Bad Design on my part... I'll know better for next time.
I resolved the issue by collapsing two queries into one. Placing the Navigation step (query 2) after the Imported Excel step (query 1) prevented Power Query from generating the Table.RemoveColumns step in the newly combined query.
I'll chalk it up to Bad Design on my part... I'll know better for next time.
Thanks edhans for the feedback. I will post this to the forum.
It is automatically removing all non-data columns. That should not cause an issue.
I would try it again. If it happens again, I would post this to the ISSUES forum. Issues - Microsoft Power BI Community
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingJoin the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the October 2025 Power BI update to learn about new features.