Showing results for 
Search instead for 
Did you mean: 

Let us put Initialize Variables into a Scope if the Scope is at the top

I get why you want Initialize actions at the top but PLEASE let me put them in a Scope at the top. Because I cant copy actions Im building a TON of variables to hold blocks of text and dynamic content that I can reuse so I have like 30 Initialize Actions at the top that I cant hide. 😞

Status: Under Review

Thank you for the suggestion.

Frequent Visitor

New power user here. I was hoping scopes could be used to organize all of my variable initialization and make my flow more readable. I was disappointed to find out that this is not the case.

New Member

I am also working on flows where i need to initialize at least 75 to 90 variables..So, If we could give them inside a scope at the top, the flow will look compact and easy to debug when any issue occurs. I would also suggest, that giving an option in the Scope settings to enable the usage of variables outside scope will be even more a better one.

Frequent Visitor

+1 for this idea --- just starting out with Power Automate and allowing variable initialization to be in a Scope will greatly help with improving readability & simplifying maintenance.

Regular Visitor

I would absolutely LOVE this. I hesitate to use variables sometimes because I dislike all the clutter it requires at the top of the flow. Alternatively, take variable initialization out of steps entirely. Maybe it's just a point of metadata about the flow. Maybe there's an accordion control which expands out somewhere where you can define variables. But having tons of variable initializations at the top of the flow is annoying. 

Kudo Collector

It would even be nicer to have only one action to define/initialize all variables of a flow.

One line per variable with three fields: Variable name, type & value (similar to "Respond to PowerApps").

Defining an action per variable and then putting it to a scope would also be annoying in the end...

Impactful Individual

@FastTrack fantastic idea! 

Frequent Visitor


Please, please, please!

Regular Visitor

Bumping this! I have 30+ variables that I would like to be able to carry into other flows, but I have to copy them each one by one! Putting them into a scope would make it all easier to read and be a HUGE time saver.

Frequent Visitor

Let's raise it!

Advocate I
Advocate I

so... Microsoft, what's taking so long to implement this most basic of feature??