Answered

Flow in PowerApps asking for too many inputs

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

Hi!

I created a flow for an approvals process and I'm using PowerApps to trigger the flow. In the flow, I primarily have many "Ask in PowerApps" inputs. When I connect to PowerApps and enter the [Flow Name].Run() function, it asks for many more inputs than I have listed in the flow?

For example my flow includes:

['Startanapproval_Details_4']

['Startanapproval_Details_5']

['Startanapproval_Details_6']

['Startanapproval_Details_7']

['Startanapproval_Details_8']

However, in PowerApps, it is asking for 8 total inputs. I've made changes within the flow so I'm thinking those first couple inputs numbered before 4 were the originals I deleted? I've removed the flow from my PowerApp and added it back but they're still there.

Is there any way to delete them? Or figure out in the flow what those first couple inputs are asking for? Without them being displayed in the flow I'm not sure if it's asking for a number, email address, name, data point...etc.

Thank you!

Caitlin

Categories:

Using flows

I have the same question (0)

All responses (10)

Answers (1)

Verified answer

Pstork1 69,129 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Once an Ask in Power Apps input has been added there really is no way to get rid of it without deleting and recreating the flow. The problem is that you created 8 inputs and then deleted several in the flow. So they are no longer in the flow, but the trigger still expects them to be there in Power Apps. You can just enter blank strings for the extra parameters or recreate the flow.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Great thank you!

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

I have this same issue but in my case I have 43 arguments where around 30 I am not using. There should be a feature to get rid of unwanted parameters when names change, it seems like something easy to fix.

Was this reply helpful? Yes No
Pstork1 69,129 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

As was stated earlier. The only way to remove parameters once they have been added using the Power Apps v1 trigger is to delete the trigger, which will delete all the parameters. Since this post was made MS has introduced a Power apps V2 trigger which doesn't use "Ask in Power Apps" and lets you manage the parameters.

Was this reply helpful? Yes No
tgabriel_ 4 on at

Like (1)

Report
Copy link

Link copied!
Hi @Pstork1,

I recently faced this same problem. My way out was the following:
export the flow as a zip file
unzip the file and open the 'definition.json' file, that contains all my flow information
once there, I manually deleted the exceeding required inputs, as showed bellow

finally, zip the file again and import it back
Hope it helps someone

Was this reply helpful? Yes No
CW 1,044 on at

Like (0)

Report
Copy link

Link copied!

Yes there is the V2 but it I'm finding it extremely buggy. It doesnt seem to provide Poawer Automate all required parameters OR Power Automate is not seeing them. It's like ping pong, back and forth and niether work with each other.

Was this reply helpful? Yes No
Pstork1 69,129 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

With the V2 trigger you define exactly which parameters get passed in the trigger using the Add Input link in the trigger. So I'm not sure what you mean when you say it doesn't provide all required parameters. You specify the parameters.

Was this reply helpful? Yes No
CW 1,044 on at

Like (0)

Report
Copy link

Link copied!

Hey Pstork. Yup, I know, but Power Automate doesn't seem to agree with either of us. I create 6, PA only sees two.

Power Apps Missing Power Automate Input Parameter - Power Platform Community (microsoft.com)

Was this reply helpful? Yes No
Torben Andresen 5 on at

Like (1)

Report
Copy link

Link copied!

I found a workaround. My flow suddenly required more than a 100 input variables. Most of them with the same name. Obviously a bug. I think it is related to working with reply to Power App. I found that if I change the settings of the initial Power Apps action in my flow, enable "Secure inputs", click done, open settings again, disable "Secure inputs" and finaly remove my input variables and add them again using "Ask Power Apps", then I'm back in business.

Was this reply helpful? Yes No
Pstork1 69,129 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

I responded to that thread. In that case it was because at least one of the parameters was a record (object) and you were putting in simple text. What does the trigger look like and did you refresh it in PA after adding additional inputs?

Was this reply helpful? Yes No