How to turn on connection within Solution?

[OmegaCaesar]

I recently learned Solutions can enable parent flows to call child flows.  I therefore created a blank solution and imported a PowerApps application into it.  From there I built new flows within the solution.  But when I run the app calling those flows I get the "connection not configured for this service" error:

Notably I get this error when I'm running the app as a standard user or as myself (the owner of the app and the flows).

Looking at my Solution I see this:

The 2 connections currently used by my flows are off.  Going through all the menus hasn't yielded a way to turn them on.  I think this might be my problem.  Is there a way to turn those on?

Those same connections are used in other flows which aren't in a solution.  And those other flows work fine.

Alternatively, am I somehow supposed to be sharing the flow differently when it's in a Solution?

The trigger is PowerApps.  For other flows (outside of Solutions) I've built with the PowerApps trigger I haven't had to share the flow.  And indeed, I do not see a way to share the flow with people unless I make them an owner.

Any insight would be greatly appreciated.

[Gopala_Krishna]

@OmegaCaesar 

I tried doing a test from my side, created a new solution --> added connection reference --> created a flow from the solution and it automatically showed me the connection reference in the connections and was also able to create and execute the flows successfully.

I was also able to trigger the flow from the power apps, though the status was showing off for the connection reference. 

The work around I would suggest will be, If you have the flow connected to a button or icon in power app copy the complete formula that you have, then remove the flow from the button by following the same process that you did for adding the flow. 

Once you remove the flow from the button re-add it again and then paste the formula that you have copied in the previous step. After this is done try to re-run the flow again and you would be able to execute the flow with out any issue.

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

if the information shared helps you, please consider giving a thumbs up 👍 and mark solution as resolved

[OmegaCaesar]

Hi @Gopala_Krishna - thanks for the advice.

I removed the flow from the button then readded it but the same problem occurred.

To really test this out I initiated a brand-new app from within the solution which just consisted of a button calling the flow.  Alas, that new app had the exact same error (Connection not configured for this service) error as the original app.  This occurred when using the new app using either a test account or my account (which created everything and is an admin).

Any other suggestions on what to try?

[Gopala_Krishna]

@OmegaCaesar 

Can you please open the flows that are making use of these connections and select any action and click on the three ellipses present on the action card. 

There you would be able to see the connection details check if the connection is intact or broken.

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

if the information shared helps you, please consider giving a thumbs up 👍 and mark solution as resolved

[OmegaCaesar]

@Gopala_Krishna 

This is the entirety of the most basic flow I'm trying to use:

Thus, only the Get File Properties action has a connection.  Here is that connection:

The black bars are just covering identical email addresses.

Originally there was only 1 Sharepoint connection but I used the "New connection reference" button to try making a new one anyway just to see if that'd help.  In both instances [using the original connection before I added a new one and using the new SP connection I made] I still got the "Connection not configured for this service" error when testing using either a test account or my admin account.

Notably, both this flow and the test app I'm using to call it were initiated within the solution rather than being created outside then imported in.

[SCTdan]

Running into the same thing, my thread for reference- https://powerusers.microsoft.com/t5/Building-Power-Apps/Connection-not-configured-for-this-service/m...

[OmegaCaesar]

FYI - I never found a solution to this issue.  Ultimately I had to make a workaround by creating a new column in Sharepoint which is functionally used to pass the information from one flow to another which I would've passed via the "Call child flow" action.  Then I simply used another new column (set as a Yes/No choice) as a trigger for what would've been the child flow - whenever the column is updated to Yes the child flow will auto-run.

Definitely not the solution I wanted but it'll do for now.

Very disappointed in Power Automate and myself for being unable to get the parent/child Solutions to work.  Will definitely make it harder for myself or anyone else to maintain.

If anyone else has something to try, please let me know.