Showing results for 
Search instead for 
Did you mean: 
Resolver I
Resolver I

Ask in Powerapp - Remove unneeded parameter



I´ve created a PowerApp, which executes a Flow.

A single Parameter is needed, to run the Flow correctly.


So I created a composition (GetID) with a variable: PowerApp - Text.

Saved the Flow, edit the PowerApp, added the Flow and no Parameter was there.

Same steps again and now I got 3 Variables, which I have to submit:

  1. SendPushNotificationCalendarIDnotfound_Parameters (Record)
  2. Compose_Input (Text)
  3. Compose_GetID (Text)

I have no Idea, why there is a parameter from my PushNotification.

Due to my second approach it is kind of understandable that I got two variables in my Composition.


But what to do with it now? I didn´t found a solution to remove the unnecessary parameter.

"Save As" did not changed anything.


Currently I helped myself out by submitting a random rec and an empty string:


But that is superfluous and hard to maintain by collegues.


It would be great to see the variables, which are asked in my powerapp, with the possibility to remove (and probably rename) them.

Or a button, which recreates all used variables.


Tanks 🙂

Community Support
Community Support

Hi @Thomas,


Thanks for your feedback.

Sometimes the Parameter will not updated automatically after Flow has been updated.

You may consider submit this as an idea under the Flow idea forum:




Community Support Team _ Michael Shao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

@v-micsh-msft wrote:


Sometimes the Parameter will not updated automatically after Flow has been updated.


Sorry I don't understand. Is the parameter supposed to go away if you stop using it in the remaining actions of your flow?


@Thomas , did you ever find a solution to this one?

Possible workaround:
Create a the flow action with the same name that produced the question, add the stale question as an answer to the correct field, then, WITHOUT removing the question, delete the entire action.

You may see a message box appearing: "This step and associated dynamic content will be deleted from this flow."  This should update the trigger so that the question is removed.

I just added a new step in flow that ask a question from powerapps, and it seems the question name is set the instant you click "ask in powerapps". I realized that what I wanted to do was not really reflecting the action in the generated question, so I removed the question and renamed the step before selecting ask in powerapps again. The previous question remained and judging from the code-view of the trigger,  this will now be required in powerapps studio. This makes little sense.

To summarize: If we do a mistake like this in flow, questions not asked must be answered powerapps studio, unless you go through every stale question and remove them as suggested in the workaround.


Advocate II
Advocate II



I have faced the same kind of issue. To fix it, I have removed the PowerApps trigger on the top of the Flow. Then all the parameters are removed.

Next steps are:

- add a new PowerApps trigger

- click on 'Ask PowerApps' on the relevant Flow actions

- fix errors in the Flow (on actions which were using the removed parameters)

- save the Flow


Please note that if you wish to see the list of parameters, using 'Peek code' (right click on the trigger), you see them in a JSON format. 

How do you "add a new Power Apps trigger"? I cannot delete my trigger, or add a new trigger.

Regular Visitor



To remove unneeded parameters I do next steps:

  1. Copy action with unneeded parameters to Clipboard
  2. Delete this action
  3. Add deleted action from Clipboard
  4. On this step you can check that parameters were deleted by running flow


Then you can change parameters





Not applicable

I faced same issue in a flow. Easy way is to delete the trigger from PowerApp step. This will remove all "Ask powerapp" parameter variables including the ones that are in use. After removal, add "trigger from Powerapp" step again and add the "Ask Powerapp parameters" again where needed. 

Regular Visitor

A workaround :
Delete the PowerApps trigger and replace it with a Manual trigger.

Save the flow.

Now replace the trigger back to PowerApps.

Frequent Visitor

Okay. Thanks for really trying to help us with this workaround explanation. But unfortunately, it is not making any sense to me. Would you be kind in posting couple of screen shots. That would be a great help. Thank you!

Helpful resources

Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

May UG Leader Call Carousel 768x460.png

June User Group Leader Call

Join us on June 28 for our monthly User Group leader call!

MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

Power Automate Designer Feedback_carousel.jpg

Help make Flow Design easier

Are you new to designing flows? What is your biggest struggle with Power Automate Designer? Help us make it more user friendly!

Top Solution Authors
Top Kudoed Authors
Users online (1,053)