Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Hi All,
So I'm fairly new to Power BI, and I'm wondering why (for curiousity's sake more than anything) when using the Advanced Editor function in the Edit Queries screen, that the M code for a step always references the previous step.
e.g. #"Removed Columns3" = Table.RemoveColumns(#"Changed Type2",{"ExitResponse"}),
Where #"Changed Type2" is was the previous step.
This caused me a couple of trip ups when writing steps by hand, so some understanding of why it's doing it would be great to help me write better code.
Thanks!
Adam
because m is a procedural langauge, therefore it creates everything in steps. The last step is all the changes in the data to that point.
Proud to be a Super User!
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
72 | |
71 | |
55 | |
37 | |
31 |
User | Count |
---|---|
89 | |
62 | |
61 | |
49 | |
45 |