I have a working flow (tested in the Flow Studio via "Test" button), also I have a PowerApp, which contains a button, by clicking on which the flow should start running. So these 2 pieces seem to work separately from each other, but once I try to connect the flow to my app, via clicking [Action -> Flows -> click on my flow] I am getting the error message saying "Failed to register the service". Please check the attached screenshot for the details. Does anyone know what is the issue?
Solved! Go to Solution.
Hi @Anonymous and @jadm ,
I have managed to register the Flow now. I tried the suggestion of exporting the Flow and then reimporting it again as an update, and that seemed to fix the problem.
A little bit more details on the app and the flow:
That's all. Please let me know, if more information is needed.
Could you please share a screenshot of your flow's configuration?
How do you get the name of the table selected in the powerapp dropdownlist within your flow?
I have made a test on my side and don't have the issue that you mentioned. The screenshot as below:
The user @mcorning has faced same issue with you, please check the response within the following thread:
Please take a try to create a new flow which uses a PowerApps button as the trigger button, then bind this flow to a Button control within your app, check if the issue is solved.
In addition, you could also take a try to add a Button control within your app, then click Action-> Flows-> "Create a new flow", after that, this Button control would be bound to a blank app which has a PowerApps Button trigger. Please check the following GIF image for more details:
Please take a try with above solution that I provided, then check if the issue is solved on your side.
Thanks for your reply! We've tried both options, which work till we add switch step in the flow. You can see our flow in the attached screenshot. I've added coments to the screenshot, answering your questions.
Do you have something issue with your flow?
If you have solved your problem, please go ahead and click “Accept as Solution” so that this thread will be marked for other users to easily identify.
No, the problem is still there. I provided an additional screenshot and the details about the flow itself in my previous response to you. We still encounter same error. You can see the screenshot in my last reply, containing all the stps, that we currently have in the flow. Just to summarize, as I mentioned in the issue description, this flow works, once we test it, but we can't bind it to the app. It seems like the issue has something to do with the "Switch" step in the flow, since once we delete this step, we can connect the flow to the app.
I'm wondering, if you have an update on this issue. Do you need more information on the problem, that we are facing? If so, please do let me know, and I'll be happy to provide you with even more details.
Looking forward for your reply!
Find your favorite faces from the community presenting at the Power Platform Community Conference!
See the latest Power Apps innovations, updates, and demos from the Microsoft Business Applications Launch Event.
ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.
Features releasing from October 2020 through March 2021