Unanswered

Flow not Connected

(1) Share

Report

Posted on by CNT

10,921 Super User 2024 Season 1

As per the new ALM update blog https://powerapps.microsoft.com/en-us/blog/key-alm-updates/ "Canvas apps that trigger flows no longer require editing the app to re-establish the connection to flows after importing a solution."

This is not working properly. I have a Canvas App which has a Flow that uses the OneDrive for Business connector. This whole thing is inside a solution. When this solution is exported to another Environment and when I (the Owner of the App & Flow) run the App, the Flow gets connected and all is well. But if another user (even a Co-owner) with whom the App is shared opens the App, the connection to the Flow is not established and it throws a Run-Time error. Can anyone throw some light into the situation?

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (0)

AndrewHolding 30 on at

Like (0)

Report

Did you end up getting anywhere with this? I am having very similar issues.

Was this reply helpful? Yes No
Irfan 164 on at

Like (3)

Report

Its still not working.
I've been using a workaround to get it working post import which works fine for now.
I am importing my solution as a manged solution.

If this is the first time you are importing your solution
Steps:
- Import the managed solution
- Open up the app.
- Remove the flow connectors
- Add a button and map your flow connectors again one by one
- Save and publish your app

If its not the first time you are importing your solution
Steps:
- Import the managed solution
- Go to App. Dont open it. Click on 3 dots and open "Show Solution Layers". Here you will see 2 layers - the unmanaged layer is your current "published" app. Remove it to make the newly imported app as currently published app.
- Open up the app.
- Remove the flow connectors
- Add a button and map your flow connectors again one by one
- Remove the button
- Save and publish your app

-Irfan

Was this reply helpful? Yes No
Yoshi1 27 on at

Like (0)

Report

It seems the flow is disconnected in app when there's a difference in flow version.
I mean if you have added a flow in an app, then later modified/updated the flow, then there's a difference of flow for the app.

I got the issue after an import to UAT, seeing some of my flows appearing as "disconnected" in my custom pages.
It was always the same flows which were in this disconnected status, the flows I had worked on recently.

Then on UAT, I deleted my solution, went back on DEV, edited my custom pages, refreshed the concerned flows (... / Refresh) and published the custompages, exported the solution, imported on UAT and tadam, no more disconnected state. Maybe it's just luck, to confirm

Was this reply helpful? Yes No
Shivani_PowerAp 19 on at

Like (0)

Report

Hi, I just resolved this similar issue by "turning On" the flows listed under my managed solution in the imported environment. Once done, publish the customizations. This will solve the issue.

Was this reply helpful? Yes No
rcarrigan 67 on at

Like (0)

Report

I'm also encountering this issue and the proposed solutions don't work for us for the following reasons:

1. RE: @Yoshi1's solution - We can't delete the solution in the target environment, as it would break all external links pointing to it.
2. RE: @Shivani_PowerAp 's solution - Our flows are being imported in the "On" state already, with all customizations published in the source environment, and all unmanaged solution layers removed from the app and flow.
3. RE: @Irfan 's workaround - this (understandably) defeats the purpose of unmanaged solutions, as it involves making intentional, albeit temporary, edits to the app in the target environment. Do you know if this workaround is still functional if you then remove the unmanaged solution layer from the app, or does it revert back?

This wasn't an issue before, so I'm curious what changed. I'm trying hard not to "throw the baby out with the bathwater", meaning stop worrying about managed vs unmanaged solutions, but issues like this make it incredibly difficult to continue advocating for ALM to my team. Hopefully, someone from the product team can provide us with a resolution that doesn't involve breaking ALM.

Was this reply helpful? Yes No