Managed solution - Powerautomate flows not activeated in Canvas app when solution is imported

[Oskarkuus]

Hi

I have a solution that i import to customers enviroments. It contains a powerapp (canvas) and a few power automate flows that are triggered from the powerapp.

I import the solution to the customers enviroment as a managed solution. The components in the solution (app, flows, connections) can not be edited in the managed solution!

Everything works, but when i run the app and try to trigger a flow from the app it says that it is not connected.
I can still open the app in the app-studio within the customers enviroment from the managed solution (but i can not save changes). So when i open the app in the app-studio i notice that none of the flows are connected, it displays an error messages just saying it is not connected. I can update the flows and they become connected! But since i can not save a managed solution i can not fix the issue, it must be imported so that this never happens!

How can i fix this?

I have searched and found several answers... most seem to require that the imported managed solution is edited, that i need to update the flow within the canvas app and then save the app. This creates a unmanaged layer that then can be deleted. But i do not allow my solutions to be edited within the customers tenants!!

How can this be fixed from the development enviroment. How to ensure that the flow that is in the canvas app is connected when the solution is imported?

[cha_cha]

It might be the connections in the flow. Try to identify what connection your flow requires. 

In my experience, I try to have everything launched within PowerApps such as sending emails as these can be done using connectors within PowerApps functions. But I'm still new to it so there might be a better way of doing it.

[Oskarkuus]

all my flows uses Office365 group connector since it calls upon graph api and then it uses the teams connector.

other than that it is very short flows just being triggered from the app.

[Oskarkuus]

This is still an issue. Some flows do not work when imorting a managed solution. The whole point is to not to edit things in each customers enviroment.

The unmanaged solution in the development enviroment do contain all connections and it contains all flows and apps that are required.

[Oskarkuus · Accepted solution]

Noticed that if i went into the app in the unmanaged solution in my development enviroment. updated the flows and then saved, published and exported a new version fo the solution...the problem sorted itself in the managed solutions in customers enviroments.

but i do not know why this suddenly worked since i had done this several times before... maybe something had changed that i dont know about. im just glad it works now.

[LimeLeaf]

I'm currently having exactly the same problem. Somehow the connections get broke during import from dev to prod environment (managed) with no logical reason.

Even the workaround of updating, reimporting or upgrading seems not to help. Very frustrating.

[Oskarkuus]

I dont have a solution really. Since my issues i havent encounterd them again...

Something you can try is to remove everything from customers tenant.

In your dev solution, make sure that all variables are unbinded and then reimport it to customer as managed solution.

I think solution have great potential but is a long way from being an good experience to manage many customers with one solution. It is far to much details you need to adjust and check in each customer to be sure everything is working.

[LimeLeaf]

@Oskarkuus 
I had a few issues that I solved today for my managed solution and it's including canvas app and flows in productive environment. I'm not quite sure if the error I was facing is really similar to yours but anyway I want to post what works for me maybe it works for you/others.

To have a better understanding of the context of my solution and it's including canvas app here some details:
I created a canvas app in an solution with multiple flows (also included in the solution) connected to it. For the most part all flows are triggered from the canvas app by using Power Apps V2 Trigger. Flows are then operating on SP Lists, Approval processes and MS Planner tasks.

Error 1: My Canvas App showed old versions of flows in the flow details page of the app in dev environment. 

Flow details page of a canvas app:

Solution for error 1: Create a fresh copy of the app with a new name by using "save as" function in power apps editor.

This solved the issue for me that old flows where showing up in the details page of my canvas app. After the fresh copy only the really connected ones where showing up.

Error 2: Error message "Connection not configured for this service" / "Für diesen Dienst ist keine Verbindung konfiguriert." in productive environment for managed solution. 

Description: Users received this error message as described in Error 2 while trying to trigger flows in my canvas app in productive environment. This made me thought that the connections between canvas app an flows where broke after I imported the solution into the productive environment as managed solution. Also the fact that the flows were not showing up anymore in the canvas app details flow page in the managed solution of the productive environment. 

As shown here:

 But I was wrong.

Solution 1 for Error 2:
My Users where receiving the error message "Connection not configured for this service" when triggering a flow from the canvas app because thy didn't had the appropriate rights in the productive environment. They were not assigned as users with an appropriate security role e.g. "basic user" to the productive environment where I imported the managed solution. 

For my part I created a Dataverse Team (Team Type) AAD Security Group in the Security Settings of the productive environment and assigned an fitting AD group and Security Role to it. 

Big shout out here for @jukkaniiranen and the following post, he briefly explains how Dataverse teams works and how you set it up: https://forwardforever.com/how-groups-teams-work-in-power-apps-dataverse/
 
Solution 2 for Error 2:
Assign the the following rights to the "basic user" security role in case you are using this role for your users / dataverse Team. 

As described in the following thread:
https://powerusers.microsoft.com/t5/Using-Connectors/connection-not-configured-for-this-service/td-p... 

Setting up all these steps led to the result for me that my users were able to finally trigger the flows from the canvas app managed solution in the productive environment.

Nevertheless I didn't got the flows showing up in the details flow page of the app in the productive environment.