Ask in Powerapps missing parameters

(2) Share

Report

Posted on by Magnus-Jansson

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.

Skärmklipp1.PNG Skärmklipp2.PNG

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.

Categories:

Using connectors

I have the same question (0)

All responses (33)

Answers (0)

v-yamao-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @Magnus-Jansson,

When testing this issue with a simple flow, I found that Recipients item doesn’t need a value from PowerApps. Please check the following screenshot. I found that only the Message field need a value from PowerApps.

I assume that when adding the flow to a button on PowerApps, we don’t need to specify a value for the Recipients item field.

You could try to run the flow to see if it will work.

Best regards,

Mabel Mao

Was this reply helpful? Yes No
Magnus-Jansson 6 on at

Like (0)

Report
Copy link

Link copied!

Try testing in a more complex flow. I do not have access to user email variable in my flow, unless I send it as a parameter when I call the flow.

You have two big differences in your example that makes it work.
1: You call the Send message function directly from the powerapp. I call a flow from my PowerApp.
2: My RecepientsItem-1 parameter is null.

Was this reply helpful? Yes No
ashu0830 8 on at

Like (0)

Report
Copy link

Link copied!

I am having same problem. variables created in flow are not showing up in powerapps.
If I am supposed to get 5 parameters in powerapps I am getting zero

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

Like (0)

Report
Copy link

Link copied!

I am getting the same error.

Was this reply helpful? Yes No
AX Learnder 10 on at

Like (0)

Report
Copy link

Link copied!

I am also facing this issue for the last 2 days. We have been using the same Microsoft Flow for the last 3 months without any issues. But starting Monday, that flow is throwing the error. We have recreated the Microsoft Flow, but still, the parameter is not getting accepted.

I think this is bug in the product itself. Hope Microsoft team is reading this.

Was this reply helpful? Yes No
ashu0830 8 on at

Like (0)

Report
Copy link

Link copied!

Did anyone has found a solution to resove this issue?.
Now, I am not getting my image parameters in powerapps which was created in microosft flow

Was this reply helpful? Yes No
bartekg 14 on at

Like (0)

Report
Copy link

Link copied!

I have the same issue:( I have been using the same Flow for the last 2 months without any issues with three parameters. Today I add fourth paramater, and now in PowerApp i see only one.

In my opinion something is wrong in flow's. I want to ask for four parameters in flow, but after reopen flow edit i see only one.

Was this reply helpful? Yes No
bartekg 14 on at

Like (0)

Report
Copy link

Link copied!

Today I talked with Office365 support about this issue. I'll let You know when I have any answer.

Was this reply helpful? Yes No
martinav 3,340 on at

Like (0)

Report
Copy link

Link copied!

I'm having the issue... Just posted another thread about it. Bottom line is... if your flow is currently working...

DO NOT SAVE IT!!!

It seems that if it is working, it will continue to work. If you save it, your flow will drop parameters.

Was this reply helpful? Yes No
AriGunawan 43 on at

Like (1)

Report
Copy link

Link copied!

I have similar issue since couple days ago.
I added some "Initialize variable" actions at the top of the flow, then ask the parameters in these actions instead of asking it directly on the actual field that needed it.
On the actual field, we can just use the variable.

It's working fine on my case, hope it's useful for anyone who needs a quick workaround.

Was this reply helpful? Yes No