Hi!
I'm doing a flow in two steps where I call an API in the first step and then notifying the user in the second step.
I'm triggering the flow from a PowerApp.
I need four parameters sent into the flow, three parameters for the api call, and one parameter (the user email) for sending the notification to the PowerApp.
In the first steg I'm creating the values with "Ask in PowerApps".
In the second step I'm creating the value for the recepients with "Ask in PowerApps".
When I look into the PowerApps section in "Dynamic Content" I can see all four parameters.
When I try to use the Flow in my PowerApp I only se the three parameters that I asked for in the first step. Is this a limitation or a bug or am I doing something wrong?
Unfortunate my browser are in swedish, but I'll try to visualize it in the pics below.
As you can see I have all four params in "Ask in PowerApps" section in Flow, but I can only see three params in my PowerApp.
What type of variable is it? string? integer??
If it wont work that way, follow with a Set Variable action, and put the Ask In Powerapps in there instead... see if that will fly. Sometimes the variable type matters... But shouldnt for a string or integer. If this is an array... that is a whole different beast. I can refer you to a different post for that if that is what you are trying to do.
I am having similar issue. I tried creating a new flow from scratch - and only 3 steps. Trigger=PowerApps; Intitalize variable1 to "Ask Powerapps", Initialize variable2 to "Ask Powerapps". Save my Flow, then reopen it in edit, variables inital value is blank....
I had a similar issue yesterday. I had to delete an action and recreate it. Perhaps re-creating the variables would have worked. Not sure. But yes, seems there is a lingering issue.
Seems to be intermitant, was able to work arround the issue this morning by deleting and re-creating the variables in flow. However I just tried to do another a few hours ago and the issue appears to be back. Did have a ticket open with PowerApps support but first line closed it as when they looked creating new variables worked arround the issue.
Do you have an update on this?
I am still facing the same issue across multiple tenancies. Is there any further info we can provde to help you identify and resolve this?
Unfortunately, this problem also occurred today.
Is this fix valid in Japan region?
Oh, I missed to read message #23, sorry.
Please ignore my reply.
I had same issue, but resolved.
In my case, some parameter named "required" and "properties" is lacked from "triggers" section of definition.json file.
(You can find this file in downloaded package archive.)
Please fix this file, then repackage and upload.
I'm sorry for my poor english.
In above case, Flow get 5 arguments flom Powerapps.
If bug is occured, some (or all) parameter (foo1~foo5) is lacked.