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:
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.
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:
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.
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.
To remove unneeded parameters I do next steps:
Then you can change parameters
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.
Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.
Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!
Check out the community blog page where you can find valuable learning material from community and product team members!