HTTP Post with Powerapps input

(0) Share

Report

Posted on by rvanderouderaa

Hi,

We are trying to send powerapps info, using microsoft flow, to an URI.

After creating the Flow with HTTP action, we want to connect the flow to the powerapp. When doing this we receive the following error:

failed to register service <GUID>

Categories:

Building Power Apps

I have the same question (0)

All responses (8)

Answers (0)

yukonn 227 on at

Like (0)

Report
Hi,

I reported this issue on MS Flow. I do believe they haven't fix. Not only this issue.
No way to pass MS Flow Uri from PowerApps.(Data typemismatch and does not has convert function)
You cannot register your MS Flow if your MS Flow Choose value is come from PowerApp.

Regards

Was this reply helpful? Yes No
Samuel on at

Like (1)

Report

Thanks for reporting this. To understand better, the first issue is that you can't use "ask in powerapps" for the URI? And for the second issue, what do you mean by "Choose value"?

Was this reply helpful? Yes No
yukonn 227 on at

Like (0)

Report

Hi,

Yes, last time we can't ask powerapps for URI. Look like fixed but i will test again. Let say, we would like to get value from powerapps when flow has condition. Here is sample.

I'm also get same error that rvanderouderaa reported error.

Was this reply helpful? Yes No
berryvanesch 2 on at

Like (0)

Report

Does anyone now if this problem is solved?

Was this reply helpful? Yes No
Samuel on at

Like (1)

Report

This is actually a known issue we're trying to work out when an input from PowerApps is used directly in an condition block. You should be able to workaround it by clicking inside any other action to ask for PowerApps input, then use that "powerapps input" token inside the condition block. This will force the proper type for the input parameter (since condition inputs are untyped, powerapps client can't bind to these inputs).

Was this reply helpful? Yes No
rvanderouderaa 2 on at

Like (0)

Report

The initial problem is the unability to connect a flow with a HTTP component to a Powerapp. Is this a known issue also?

Was this reply helpful? Yes No
Samuel on at

Like (1)

Report

Yes, this is the same root cause. The "Body" parameter of the HTTP action is untyped, so PowerApps doesn't know how to bind to it. Theoretically, you can do the same workaround as above to force the input to a particular type (probably a string), but that's less practical for part of an HTTP payload. We have work booked to figure out a better story for these cases.

Was this reply helpful? Yes No
jovanC 2 on at

Like (0)

Report

Hi Samuel,

Is the issue resolved yet? Is there a better way to get input from PowerApps to HTTP action in flow now?

Was this reply helpful? Yes No