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>
Hi Samuel,
Is the issue resolved yet? Is there a better way to get input from PowerApps to HTTP action in flow now?
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.
The initial problem is the unability to connect a flow with a HTTP component to a Powerapp. Is this a known issue also?
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).
Does anyone now if this problem is solved?
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.
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"?
Hi,
I reported this issue on MS Flow. I do believe they haven't fix. Not only this issue.
Regards
WarrenBelz
146,609
Most Valuable Professional
RandyHayes
76,287
Super User 2024 Season 1
Pstork1
65,946
Most Valuable Professional