Automatic multiple values created for one variable initialization?

[CCava]

Hi,

I'm working on updating a few of my flows and kept running into an issue.  So I decided to start fresh and see if it still happens - it does.  I am using an instant/button flow from Power Apps.  I have several data points which exist in the Power App that I  need for the flow, such as Researcher Name, Researcher Email, etc. 

Previously, I start the flow with the trigger as "Power Apps".  Then I initialize variables I need, and in the value, I choose "Ask in Power Apps".  And that was that.  

Now, when I do  the same thing, instead of just creating one value for that variable, it creates multiple variables (see below) and chooses a random one for me to use. 

Also in the Power App run, it lists all other values (and odd multiple values) from the flow, outside of what I said to ask for in Power Apps.  Here, I have only chosen "Ask in Power Apps for 6 items, and I have over 80 to add a value for in the Power Apps FlowName.Run() - I know I can use "" to skip over one, but that's not the point:

Has something changed that is making this happen? Is there a way to turn that off? I am lost as to why this is happening. Thanks for your help!

-C

[CCava]

Based on the Top Solution Authors for last month, I'd like to ask @Expiscornovus , @Mira_Ghaly , and @Pstork1 if any of them have ideas regarding this?

Thanks!

C

[v-jefferni]

Hi @CCava ,

Have you ever modified the variables content from selecting new "Ask in PowerApps"? Each time you select a dynamic content and save the flow, in PowerApps button trigger will automatically generate a parameter for actions to use. So, for PowerApps button trigger, if you would like to modify the flow, the best approach will be delete the original trigger then add a new one, select "Ask in PowerApps" in actions again and save the flow.

Hope this helps.

Best regards,

Community Support Team _ Jeffer Ni
If this post helps, then please consider Accept it as the solution to help the other members find it.

[CCava]

Thanks for your idea.  I have actually started a completely new flow, with a new trigger (same option), and this happens immediately with the first Initialize variable action that in the value section, I select "Ask in Power Apps".  Unfortunately, based on this, I don't think deleting the original trigger will help when it happens again on a fresh flow when I use the trigger.  Thanks for your idea.

-C

[CCava · Accepted solution]

I found a solution to the issue.  I had experimental features turned on - and have for quite a while with no issues, until now.  After turning it off, things have returned to normal, but now I need to remake any of my flows with the Ask in Power Apps that have the additional values.  

-C