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!Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes! Register now.
I'm super annoyed by how IntelliSense works as described below. Does anyone know a trick?
= PreviousStep
// I want to get the row count of the resultig table in PreviousStep
// I will start typing "Table.R" right before "PreviousStep" like this:
= Table.RPreviousStep
// When I hit Tab it overwrites the value that I wanted to include, resulting in this:
= Table.RowCount
// Nooooooooooooooooooooooooooooooooooooooooooo 😞
Hi @richard-powerbi ,
You could vote for this idea to improve Power Query.
https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/33129547-intellisense-for-m
@v-eachen-msft don't we have it? https://ssbi-blog.de/blog/technical-topics-english/intellisense-for-power-query-m-finally/
I'm complaining about how it works.
Before typing live the space in front of your step, this will allow you to use the Intellisense and keep the step, but you still will need to delete parentheses at the end of the function.
I find it annoying too.
@Mariusz Am I crazy or has it been fixed? 😆 I'm not having the problem anymore. Latest version from Store.
@Mariusz I was crazy. It has not been fixed. But it seems to work fine when the next character is a #.
So a workaround would be to make sure your steps consist of two words or manually give the step #"".
On a sidenote, anyone knows if it is possible to force PQ to give steps always #""?
@Mariusz yeah that's what I'm doing or sometimes I cut the value and hit tab and paste the value... was hoping there was a better trick.
You and me both 🙂