This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreGet Fabric Certified for FREE during AI Skills Fest. This week only. Secure your voucher now.
After I create a new step, I want to be able to rename the step to document the purpose of the step. However, I have to wait for the step to completely execute first. This can cause a delay of several seconds for a complicated query, and if I'm adding several steps in sequence, this adds up. Other commands on the query step are available without waiting, but I'd like Rename to be included in those commands.
I know I can skip the wait by using Advanced Editor, but then I have to edit the name in multiple locations to ensure that I don't break the query.
Solved! Go to Solution.
The Advanced Editor approach you mentioned is the only current workaround, but you are right that it requires updating the step name in two places.
You can actually save a bit of time by right-clicking the step, going to properties and rename the step from there.
My Power BI is set in French but it should be the same order: on the screenshot you can see that the "Rename" (Renommer) option is greyed out as the query is loading but "Properties" (Propriétés) is still clickable. This even allows you to type in a short description of what your step is doing which is always a good practice when documenting your code 🙂
However this is still a bit tedious. I wish Power BI offered a native option to automatically change step names to custom names (for ex "Remove other columns" to "SelectCol") because the default names are quite long and filled with spaces which creates this irritating #"Step name" format
Hi @joespiff ,
We wanted to kindly follow up regarding your query. If you need any further assistance, please reach out.
Thank you.
I meant to post this in the ideas area for Power BI, not in the help forum. When I discovered my mistake, I posted it there as well. I apologize for the confusion. The responses were worth considering, but ultimately did not address my intent, which was to suggest a development improvement that would save a bit of time for people who are trying to make their query step names function as a form of documentation.
You can actually save a bit of time by right-clicking the step, going to properties and rename the step from there.
My Power BI is set in French but it should be the same order: on the screenshot you can see that the "Rename" (Renommer) option is greyed out as the query is loading but "Properties" (Propriétés) is still clickable. This even allows you to type in a short description of what your step is doing which is always a good practice when documenting your code 🙂
However this is still a bit tedious. I wish Power BI offered a native option to automatically change step names to custom names (for ex "Remove other columns" to "SelectCol") because the default names are quite long and filled with spaces which creates this irritating #"Step name" format
I agree that it would be nice to have this option, although I would tend to change my step names in the opposite direction. When I intend to develop a report and then hand it to someone else to maintain, I would like the step names to describe what they are doing in more detail.
Your answer was exactly what I needed, thank you!
Hi @joespiff ,
Thanks for reaching out to Microsoft Fabric Community.
Just wanted to check if the responses provided were helpful. If further assistance is needed, please reach out.
Thank you.
The Advanced Editor approach you mentioned is the only current workaround, but you are right that it requires updating the step name in two places.
@joespiff please try adding a temporary step at the beginning where you keep only the first n rows (for example the 3 first rows) , then try changing the names of the steps.
Did you try with Disable Data Preview in Editor: Navigate to File > Options and settings > Options > Data Load and uncheck Allow data preview to download in the background?
Hi @joespiff
In Power Query, you can not rename an applied step until it finishes executing as this is by design because the engine validates the step before allowing edits.
To reduce delays, you can disable background data preview like File - Options - Data Load
Hi @joespiff,
thanks for reaching out to the community.
I havent seen this behaviour until now but I guess this is by design. As you mentioned the onyl workaround may the advanced editor.
Maybe its good to put this as an idea in the ideas section here: Fabric Ideas - Microsoft Fabric Community
Best regards!
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 25 | |
| 24 | |
| 22 | |
| 19 | |
| 18 |
| User | Count |
|---|---|
| 43 | |
| 42 | |
| 41 | |
| 21 | |
| 21 |