I understand the current limitation on renaming an Action that has subsequent actions that depend upon it.
I'd like functionality to be implemented that will refactor the flow (rename subsequent uses of the Action's output) when a rename occurs, so that I can rename an Action that has dependencies upon it.
Kind of like how in Visual Studio, I can select a variable name, right click and select rename and it will rename all uses of the variable.
This item was completed last year - see this update: https://docs.microsoft.com/en-us/business-applications-release-notes/April19/microsoft-flow/change-a...
Absolutely agree. And linking a related 'idea' (below) for anyone else interested, and to vote for both to be implemented.
Or like any other file. You could argue that all files have dependencies of sorts. So yes, totally agree rename option is needed. For Microsoft to try and defend the flawed status quo would be absurd.
We need the ability to change the name of a flow step after it has been used. Flow should auto-correct the downstream references.
We are working on improving this experience. Thank you.
@Stephen I think this is released?
It is happening for me in many cases, but not all. Particularly frustrating in For each loops that don't seem to update.
I love how we are 17 months on from an update of 'Started' and it still hasn't been rolled out.
@Stephen , any update on when we can expect this?
@Stephen - Can you please provide an update on this?
I am not sure displaying a warning message if you rename a step and having the ability to rename a step are the same thing?