Initialization Variable NOT going away, No Longer Used or Referrenced

[schuess3]

I have a flow triggered by PowerApps. I have a few Variable Initialization actions that were setup as "Ask PowerApps". There seems to be an old, outdated variable input created that is no longer used or referrenced that is not going away. PowerApps it is still forcing me to put in a value, but i am 99% positive it is no longer referrenced in the flow. Is there a way I can clean that up?

[v-yamao-msft]

Hi @schuess3 ,

The issue could be reproduced by me.

If I just remove dynamic content “Ask in PowerApps” for the Initialize variable action, PowerApps will still ask a value for it.

I will help report it from my side.

By the way, I found that removing the Initialize variable action then re-add it to the flow, PowerApps won’t ask for a value anymore.

Please take a try with it on your side.

Best regards,

Mabel

[v-yamao-msft]

Hi @schuess3 ,

The issue has been reported.

I will back to you once I got any updates later.

Best regards,

Mabel

[v-yamao-msft · Accepted solution]

Hi @schuess3 ,

I have some updates for you.

This is a known issue for the PowerApps button. Please try to restart the process in order to get this to work.

A fix will be rolled out in the future but I don’t have an ETA currently.

Please try with the workaround to see if it works.

Best regards,

Mabel

[KC]

Work around is not working for me.

Any word on an ETA for when this will be fixed would be appreciated.

[KC]

OK, I just realized that if you add a Initialize Variable step, before anything else, you need to rename the title of the step using the elipsis button.

Change the Step Title: Initialize Variable to YourVar name.

Then copy YourVar into the Name field  

In the Value field, select Ask in PowerApps and then your var name will be put into Value field as YourVar_Value

Be careful, if you introduce a new Initialize var and forget the steps above then the default Initializevariable_Value will be part of your parameter set in PowerApps for that Flow. 

It would be great if we could delete the default var from the Flow Editor.

[Anonymous]

I'm having the same problem. Can't get rid of "Initializevariable_Value". Now my app button is looking for that and giving me an Invalid Number of Arguments error. I already recreated the entire Flow from scratch to solve this error earlier. Basically can't initialize any variables without breaking the thing. 

[Naboo]

Hi All,

it seems that this problem is still not solved and the above solution does not work for me in the current version of power automate?!?

Add InitVar in PowerAutomate does automatically create a var "Initializevariable_Value" even if i rename the action immideately:


If i add "Ask in PowerApps" in the Value field - flow add a second variable in the list (and does NOT remove the old one):
Flow caches the old var

PowerApps remember all the variables (also REMOVED vars):

...i tried also to remove the "Init Var" Action in flow - save it - edit again - add action again - save - recreate connection in powerapps... nothing worked. 

Any ideas to get this work?

thanks in advance, Markus

[janbakker]

I have the same issue. The only "fix" for this, is to re-create your flow, and carefully take thi steps:

0. Think about the variables you need. Deleting or changing them afterward is a big pain (as we can all read above)

1. Initialize new variable (don't pick the value just yet!)

2. Rename the step into a logic name

3. Now select Ask In PowerApps for the value.

[Anonymous]

The issue remains two years later. I wonder when this will get fixed....In the meantime I will have to recreate my flow.

[FORME_RH]

What worked for me was to remove the first step (Trigger) "PowerApps" and then add it again. After that you will have to set the "Value"-field in the variables again (choose: "Ask in PowerApps"). That whay you don't have to build the flow all over. It solved the issue for me.

[ErwanF]

Please pin this as answer. This is more logical solution to the op problem.

[Anonymous]

Can you explain a bit more exactly what you "removed" and then added again?

[ErwanF]

Hi @Anonymous,

Delete the trigger or first step of your flow and then add it again. This of course you have to reinitialise all variable that is associated with ask in powerapps. When you reinitialise, required field in the trigger will be filled if you select for .

Modifying your variable name will produce the OP issue. If you peek json at the trigger, you will see an extra field that is initialised but not declared when running the flow.Run().  The code is basically parameter for function per se. 

[Johnolnes]

The delete the first step as @FORME_RH explained worked perfectly.

Thank you!