cancel
Showing results for 
Search instead for 
Did you mean: 

PowerApps integration - Remove/Rename parameters

When you use PowerApps to trigger a flow, once you select "Ask in PowerApps" in an action, it creates a parameter.  In the "Run" function in PowerApps, you then have to specify the values of those parameters.

 

Trouble is, when you're refactoring both the Flow and the PowerApp, there's no way to either rename or remove the parameters.  For instance, if you delete an action that previously used a "As in PowerApps" value (which creates a parameter), the parameter still exists!

 

Could we place have a way of maintaining the list of parameters?

 

This has been posted as a bug previously by @Thomashttps://powerusers.microsoft.com/t5/I-Found-A-Bug/Ask-in-Powerapp-Remove-unneeded-parameter/m-p/6513...

 

Also, it has been posted as an idea to in PowerApps Ideas by @JanSomers91.  Please also vote for that idea if you vote for this idea!

 

Thanks!

 

Status: Planned

We plan on letting you configure parameters for PowerApps flows just like you can for Flow mobile buttons.

Comments
Level: Powered On

Very important feature!

Level: Powered On

I have exactly the same problems like you -_-

Level 8

Please fix, another example of a workaround that requires deleting a step and re-adding just to get rid of something = wasted time. Thanks!

Level: Powered On

I couldn't agree more. My work arounds:

 

Naming PowerApp Variables

  1. Add the step, such as Execute SQL stored procedure
  2. Rename your step (using the elipses) to a name that you want to prefix your variables with, such as SalesOrder (sadly you can't seem to rename a step if it is the first step in the flow)
  3. Locate your stored procedure (sp)
  4. In each sp parameter box, use the Dynamic content -> See more option, this reveals the Ask in PowerApps option, which is a somewhat obscure.
  5. Click the Ask in PowerApps option to generate the variable name which will be in the format: StepName_StoredProcedureParameterName. For instance, in step two, I renamed the step to be SalesOrder, and assuming an sp parameter name of OrderNumber, I end up with the PowerApp variable name: SalesOrder_OrderNumber, which is much more meaningful in the PowerApps editor.
  6. Repeat steps 4 & 5 for each sp parameter
  7. Rename the Step again if required. You may wish to rename your step back to something more meaningful in Flow, such as Execute sp_AddSalesOrder procedure for instance

 

Removing Unwanted PowerApp Variables
As @mcolbert said, delete the Step and recreate it. This doesn't always work, and you may have to delete the step, save the Flow, close it, reopen it, add the Step again. Not annoying in the least... Sigh.

 

Persisting Parameters
In my case, I had created two default parameters. Wanting to rename these, I followed the steps above and created two new parameters with the names that I wanted. All well and good, I now had two parameters with names that I wanted to use and no references to the old default named parameters. Having tested, saved and closed the Flow, I opened the flow in PowerApps and, low and behold, there were 4 parameters listed, both my nicely named ones and the default ones. There was no way that I could find of removing the unwanted parameters. I was forced to recreate the Flow from scratch, and then the flow name had changed... Not a great experience.

 

Kaine

Power Automate Staff
Status changed to: Planned

We plan on letting you configure parameters for PowerApps flows just like you can for Flow mobile buttons.

Level: Power Up

Hello,

 

While waiting for the microsoft solution here is the manual workaround. 

Download the workflow as ZIP package.

Go inside and find definition.json. Open it in a json editor rename or remove the parameter you dont like.

Save and put the file back to the Zip Package and update your flow with this. 

 

Works as charm.

Have fun guys

 

Level: Powered On

This has been incredibly cumbersome for quite a while.  I was using flow studio, but now that they're charging a subscription I might build a powershell script for extracting the correct json file and making the edit.  If I do, I'll share.

Level 8

Would be nice if you could simply edit in the peek code window. Kind of like the Advanced configuration.

JD1
Level: Powered On

.

Level: Power Up

I have found of solution for this issue(might help someone) :- 

1 .First you need to go to all the Intialise variables in flow and replace the value field with a dummy string value.  
2. Save your flow.
3. Add a new step of initialise variable and check for what options you see in the "Ask in powerapps"
4. Delete this variable step you just added.
5. Go to all the variables now and delete the dummy value and replace with new Variables in 'Ask in PowerApps".
6. Now the 'order' of the variables in your call might not work from power apps , so you will need to change the order of variables in your call and then your are set.

Cheers.
Joy